# 객체 생성과 파괴

- [아이템1 생성자 대신 정적 팩터리 메서드를 고려하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-1item.md): Effective Java 3e 아이템 1을 요약한 내용 입니다.
- [아이템2 생성자에 매개변수가 많다면 빌더를 고려하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-2item.md): Effective Java 3e 아이템 2를 요약한 내용 입니다.
- [아이템3 private 생성자나 열거 타입으로 싱글턴임을 보증하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-3item.md): Effective Java 3e 아이템 3를 요약한 내용 입니다.
- [아이템4 인스턴스화를 막으려거든 private 생성자를 사용하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-4item.md): Effective Java 3e 아이템 4를 요약한 내용 입니다.
- [아이템5 자원을 직접 명시하지 말고 의존 객체 주입을 사용하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-5item.md): Effective Java 3e 아이템 5를 요약한 내용 입니다.
- [아이템6 불필요한 객체 생성을 피하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-6item.md): Effective Java 3e 아이템 6를 요약한 내용 입니다.
- [아이템7 다 쓴 객체 참조를 해제하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-7item.md): Effective Java 3e 아이템 7를 요약한 내용 입니다.
- [아이템8 finalizer와 cleaner 사용을 피하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-8item.md): Effective Java 3e 아이템 8를 요약한 내용 입니다.
- [아이템9 try-finally보다는 try-with-resources를 사용하라](https://incheol-jung.gitbook.io/docs/study/effective-java/undefined/2020-03-20-effective-9item.md): Effective Java 3e 아이템 9를 요약한 내용 입니다.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://incheol-jung.gitbook.io/docs/study/effective-java/undefined.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.