- ホーム
- > 洋書
- > 英文書
- > Computer / Languages
基本説明
Josh Bloch designed, implemented, and maintained many of the Java platform libraries. Here he shares 57 "nuggets"--rules and code examples showing what works, what doesn't, and how to use the language and its libraries to best effect.
Full Description
Are you looking for a deeper understanding of the Java (TM) programming language so that you can write code that is clearer, more correct, more robust, and more reusable? Look no further! Effective Java (TM), Second Edition, brings together seventy-eight indispensable programmer's rules of thumb: working, best-practice solutions for the programming challenges you encounter every day.This highly anticipated new edition of the classic, Jolt Award-winning work has been thoroughly updated to cover Java SE 5 and Java SE 6 features introduced since the first edition. Bloch explores new design patterns and language idioms, showing you how to make the most of features ranging from generics to enums, annotations to autoboxing.Each chapter in the book consists of several "items" presented in the form of a short, standalone essay that provides specific advice, insight into Java platform subtleties, and outstanding code examples. The comprehensive descriptions and explanations for each item illuminate what to do, what not to do, and why.Highlights include: New coverage of generics, enums, annotations, autoboxing, the for-each loop, varargs, concurrency utilities, and much more Updated techniques and best practices on classic topics, including objects, classes, libraries, methods, and serialization How to avoid the traps and pitfalls of commonly misunderstood subtleties of the language Focus on the language and its most fundamental libraries: java.lang, java.util, and, to a lesser extent, java.util.concurrent and java.io Simply put, Effective Java (TM), Second Edition, presents the most practical, authoritative guidelines available for writing efficient, well-designed programs.
Contents
Foreword xiPreface xiiiAcknowledgments xviiChapter 1: Introduction 1Chapter 2: Creating and Destroying Objects 5Item 1: Consider static factory methods instead of constructors 5Item 2: Consider a builder when faced with many constructorparameters 11Item 3: Enforce the singleton property with a private constructor 17Item 4: Enforce noninstantiability with a private constructor 19Item 5: Avoid creating unnecessary objects 20Item 6: Eliminate obsolete object references 24Item 7: Avoid finalizers 27Chapter 3: Methods Common to All Objects 33Item 8: Obey the general contract when overriding equals 33Item 9: Always override hashCode when you override equals 45Item 10: Always override toString 51Item 11: Override clone judiciously 54Item 12: Consider implementing Comparable 62Chapter 4: Classes and Interfaces 67Item 13: Minimize the accessibility of classes and members 67Item 14: In public classes, use accessor methods, not public fields 71Item 15: Minimize mutability 73Item 16: Favor composition over inheritance 81Item 17: Design and document for inheritance or else prohibit it 87Item 18: Prefer interfaces to abstract classes 93Item 19: Use interfaces only to define types 98Item 20: Prefer class hierarchies to tagged classes 100Item 21: Use function objects to represent strategies 103Item 22: Favor static member classes over nonstatic 106Chapter 5: Generics 109Item 23: Don't use raw types in new code 109Item 24: Eliminate unchecked warnings 116Item 25: Prefer lists to arrays 119Item 26: Favor generic types 124Item 27: Favor generic methods 129Item 28: Use bounded wildcards to increase API flexibility 134Item 29: Consider typesafe heterogeneous containers 142Chapter 6: Enums and Annotations 147Item 30: Use enums instead of int constants 147Item 31: Use instance fields instead of ordinals 158Item 32: Use EnumSet instead of bit fields 159Item 33: Use EnumMap instead of ordinal indexing 161Item 34: Emulate extensible enums with interfaces 165Item 35: Prefer annotations to naming patterns 169Item 36: Consistently use the Override annotation 176Item 37: Use marker interfaces to define types 179Chapter 7: Methods 181Item 38: Check parameters for validity 181Item 39: Make defensive copies when needed 184Item 40: Design method signatures carefully 189Item 41: Use overloading judiciously 191Item 42: Use varargs judiciously 197Item 43: Return empty arrays or collections, not nulls 201Item 44: Write doc comments for all exposed API elements 203Chapter 8: General Programming 209Item 45: Minimize the scope of local variables 209Item 46: Prefer for-each loops to traditional for loops 212Item 47: Know and use the libraries 215Item 48: Avoid float and double if exact answers are required 218Item 49: Prefer primitive types to boxed primitives 221Item 50: Avoid strings where other types are more appropriate 224Item 51: Beware the performance of string concatenation 227Item 52: Refer to objects by their interfaces 228Item 53: Prefer interfaces to reflection 230Item 54: Use native methods judiciously 233Item 55: Optimize judiciously 234Item 56: Adhere to generally accepted naming conventions 237Chapter 9: Exceptions 241Item 57: Use exceptions only for exceptional conditions 241Item 58: Use checked exceptions for recoverable conditions and runtime exceptions for programming errors 244Item 59: Avoid unnecessary use of checked exceptions 246Item 60: Favor the use of standard exceptions 248Item 61: Throw exceptions appropriate to the abstraction 250Item 62: Document all exceptions thrown by each method 252Item 63: Include failure-capture information in detail messages 254Item 64: Strive for failure atomicity 256Item 65: Don't ignore exceptions 258Chapter 10: Concurrency 259Item 66: Synchronize access to shared mutable data 259Item 67: Avoid excessive synchronization 265Item 68: Prefer executors and tasks to threads 271Item 69: Prefer concurrency utilities to wait and notify 273Item 70: Document thread safety 278Item 71: Use lazy initialization judiciously 282Item 72: Don't depend on the thread scheduler 286Item 73: Avoid thread groups 288Chapter 11: Serialization 289Item 74: Implement Serializable judiciously 289Item 75: Consider using a custom serialized form 295Item 76: Write readObject methods defensively 302Item 77: For instance control, prefer enum types to readResolve 309Item 78: Consider serialization proxies instead of serialized instances 313Appendix: Items Corresponding to First Edition 317References 321Index of Patterns and Idioms 327Index 331
