<rt id="bn8ez"></rt>
<label id="bn8ez"></label>
  • 

    • <span id="bn8ez"></span>
    

    <label id="bn8ez"><meter id="bn8ez"></meter></label>
    

    
    

    




    







												


        

    
	

    Vincent.Chan‘s Blog
    

    

    


    
	
		

    常用鏈接
    

		

    統計
    
	
		

    積分與排名
    


		
		
    網站
    
		
				
			
	

		

    最新評論
	
    

		
	

    

    
	
					
	
    
		
    
			《Effective Java》Chapter 2
		
    
		Chapter 2. Creating and Destroying Objects

    Item 1: Consider providing static factory methods instread of constructs
    eg. A static factory method from the class Boolean, which translates a boolean primitive value into a Booleam object reference:
    

    public static Boolean valueOf(boolean b) {
            return (b ? Boolean.TRUE : Boolean.FLASE);
    }
    Advantages:
    a) unlike constructors, they have names.
    b) unlike constructors, they are not required to create a new object each time they're invoked.
    c) unlike constructors, they can return an object of any subtype of their return type.     (Atten plz: in JDK 5.0, there is Covariant Return Types)
    Disadvantages:
    a) classes without public or protected constructors cannot be subclassed.
    b) they are not readily distinguishable from other static methods.
       two names for static factory methods are becoming common:
          valueOf --- Return an instance that has, loosely speaking, the same value as its parameters.
          getInstance --- Return an instance that is described by its parameters but cannot be said to have the same value.

    Item 2: Enforce the singleton property with a private constructor
    One approach, the public static member is a final field:
    

    // Singleton with final field
    public class Elvis {
            public static final Elvis INSTANCE = new Elvis();
        
            private Elvis() {
            
        }
        
             // Remainder omitted
    }
    A second approach, a public static factory method is provided instead of the public static final field:
    

    // Singleton with static factory
    public class Elvis {
            private static final Elvis INSTANCE = new Elvis();
        
            private Elvis() {
            
        }
        
            public static Elvis getInstance() {
                return INSTANCE;
        }
        
             // Remainder omitted
    }

    Item 3: Enforce noninstantiability with a private constructor
    Attemping to enforce noninstantiablity by making a class abstract does not work.
    A class can be made noninstantiable by including a single explicit private constructor:
    

    // Noninstantiable utility class
    public class UtilityClass {
        
            // Suppress default constructor for noninstantiability
        private UtilityClass() {
                // This constructor will never be invoked
        }
        
             // Remainder omitted
    }

    Item 4: Avoid creating duplicate objects
    An object can always be reused if it is immutable.
    As an extreme example of what not to do:  

    String s = new String("silly"); // DON'T DO THIS!
    The improving version is simply the following:  

    String s = "No longer silly"
    You can often avoid creating duplicate objects by using static factory methods (Item 1) in preference to constructors on immutable classes that provide both.
    

    public class Person {
            private final Date birthDate;

            // Other fields omitted
        public Person(Date birthDate) {
                this.birthDate = birthDate;
        }

            // DON'T DO THIS!
        public boolean isBabyBoomer() {
            Calendar gmtCal     = Calendar.getInstance(TimeZone.getTimeZone("GMT"));
            gmtCal.set(    1946, Calendar.JANUARY, 1, 0, 0, 0);
            Date boomStart     = gmtCal.getTime();
            gmtCal.set(    1965, Calendar.JANUARY, 1, 0, 0, 0);
            Date boomEnd     = gmtCal.getTime();
                return birthDate.compareTo(boomStart) >= 0
                        && birthDate.compareTo(boomEnd) < 0;
        }
    }
    The isBabyBoomer method unnecessarily creates a new Calendar, TimeZone, and two Date instances each time it is invoked. The version that follows avoids this inefficiency with a static initializer:
    

    class Person {
            private final Date birthDate;

            public Person(Date birthDate) {
                this.birthDate = birthDate;
        }

            /**
         * The starting and ending dates of the baby boom.
             */
            private static final Date BOOM_START;

            private static final Date BOOM_END;
            static {
            Calendar gmtCal     = Calendar.getInstance(TimeZone.getTimeZone("GMT"));
            gmtCal.set(    1946, Calendar.JANUARY, 1, 0, 0, 0);
            BOOM_START     = gmtCal.getTime();
            gmtCal.set(    1965, Calendar.JANUARY, 1, 0, 0, 0);
            BOOM_END     = gmtCal.getTime();
        }

            public boolean isBabyBoomer() {
                return birthDate.compareTo(BOOM_START) >= 0
                        && birthDate.compareTo(BOOM_END) < 0;
        }
    }

    Item 5: Eliminate obsolete object reference
    

    // Can you spot the "memory leak"?
    public class Stack {
            private Object[] elements;

            private int size = 0;

            public Stack(int initialCapacity) {
                this.elements = new Object[initialCapacity];
        }

            public void push(Object e) {
            ensureCapacity();
            elements[size    ++] = e;
        }

            public Object pop() {
                if (size == 0)
                    throw new EmptyStackException();
                return elements[--size];
        }

            /**
         * Ensure space for at least one more element, roughly doubling the capacity
         * each time the array needs to grow.
             */
            private void ensureCapacity() {
                if (elements.length == size) {
                Object[] oldElements     = elements;
                elements     = new Object[2 * elements.length + 1];
                System.arraycopy(oldElements,     0, elements, 0, size);
            }
        }
    }
    If
a stack grows and then shrinks, the objects that were popped off the
stack will not be garbage collected, even if the program using the
stack has no more references to them. This is because the stack
maintains obsolete references to these objects.
    

    public Object pop() {
            if (size==0)
                throw new EmptyStackException();
        Object result     = elements[--size];
        elements[size]     = null; // Eliminate obsolete reference
        return result;
    }

    Item 6: Avoid finalizers
    Nothing time-critical should ever be done by a finalizer.
    You should never depend on a finalizer to update critical persistent state.
    Explicit termination methods are often used in combination with the try-finally construct to ensure prompt termination.
    

    Foo foo = new Foo();
    try {
            // Do what must be done with foo
        
    }     finally {
        foo.terminate();     // Explicit termination method
    }
    It is important to note that “finalizer chaining” is not performed automatically. If a class (other than Object) has a finalizer and a subclass overrides it, the subclass finalizer must invoke the superclass finalizer manually.
    

    // Manual finalizer chaining
    protected void finalize() throws Throwable {
            try {
                // Finalize subclass state
            
        }     finally {
                super.finalize();
        }
    }
    Instead
of putting the finalizer on the class requiring finalization, put the
finalizer on an anonymous class (Item 18) whose sole purpose is to
finalize its enclosing instance. A single instance of the anonymous
class, called a finalizer guardian, is created for each instance of the enclosing class.
    

    // Finalizer Guardian idiom
    public class Foo {
            // Sole purpose of this object is to finalize outer Foo object
        private final Object finalizerGuardian = new Object() {
                protected void finalize() throws Throwable {
                    // Finalize outer Foo object
                
            }
        }    ;
             // Remainder omitted
    }
    
		
    
			posted on 2006-02-18 18:31 Vincent.Chen 閱讀(177) 評論(0)  編輯  收藏  所屬分類: Java 
		
    
	
    
	
	


	


    
	    
    




    








    

				

    




    







    
        
	



主站蜘蛛池模板：
女人被男人桶得好爽免费视频
|
亚洲国产精品13p|
国产91免费视频|
国产成人A在线观看视频免费|
免费涩涩在线视频网|
亚洲日韩VA无码中文字幕|
精品久久香蕉国产线看观看亚洲|
亚洲欧洲免费视频|
真人做A免费观看|
亚洲Aⅴ无码一区二区二三区软件|
亚洲AV无码专区在线播放中文|
波多野结衣亚洲一级|
亚洲AV成人无码久久WWW|
久久久久免费视频|
丁香花免费完整高清观看|
无码欧精品亚洲日韩一区夜夜嗨|
国产成人综合久久精品亚洲|
免费中文字幕不卡视频|
亚洲国产一区在线|
日韩一级视频免费观看|
亚洲av中文无码乱人伦在线咪咕|
日韩成人免费视频|
亚洲Aⅴ无码一区二区二三区软件|
h片在线播放免费高清|
好爽又高潮了毛片免费下载|
亚洲AV无码专区在线观看成人|
www亚洲一级视频com|
99在线热播精品免费99热|
国产精品冒白浆免费视频|
亚洲av无码电影网|
无码日韩精品一区二区三区免费|
亚洲美女一区二区三区|
美丽姑娘免费观看在线观看中文版|
在线观看人成网站深夜免费|
色网站在线免费观看|
91高清免费国产自产|
鲁死你资源站亚洲av|
亚洲av无码av制服另类专区|
免费看韩国黄a片在线观看|
一区视频免费观看|
日本免费观看网站|