Mutable and Immutable Objects


Mutable Objects: When you have a reference to an instance of an object, the contents of that instance can be altered
Immutable Objects: When you have a reference to an instance of an object, the contents of that instance cannot be altered


Immutability and Instances

To demonstrate this behaviour, we'll use java.lang.String as the immutable class and java.awt.Point as the mutable class.
 Point myPoint = new Point( 0, 0 );
 System.out.println( myPoint );
 myPoint.setLocation( 1.0, 0.0 );
 System.out.println( myPoint );

 String myString = new String( "old String" );
 System.out.println( myString );
 myString.replaceAll( "old", "new" );
 System.out.println( myString );
In case you can't see what the output is, here it is:
 java.awt.Point[0.0, 0.0]
 java.awt.Point[1.0, 0.0]
 old String
 old String
We are only looking at a single instance of each object, but we can see that the contents of myPoint has changed, but the contents of myString did not. To show what happens when we try to change the value ofmyString, we'll extend the previous example.
 String myString = new String( "old String" );
 System.out.println( myString );
 myString = new String( "new String" );
 System.out.println( myString );
The output from this is:
 old String
 new String
Now we find that the value displayed by the myString variable has changed. We have defined immutable objects as being unable to change in value, so what is happening? Let's extend the example again to watch the myString variable closer.
 String myString = new String( "old String" );
 String myCache = myString;
 System.out.println( "equal: " + myString.equals( myCache ) );
 System.out.println( "same:  " + ( myString == myCache ) );

 myString = "not " + myString;
 System.out.println( "equal: " + myString.equals( myCache ) );
 System.out.println( "same:  " + ( myString == myCache ) );
The result from executing this is:
 equal: true
 same:  true
 equal: false
 same:  false
What this shows is that variable myString is referencing a new instance of the String class. The contents of the object didn't change; we discarded the instance and changed our reference to a new one with new contents.

Source: http://www.javaranch.com/journal/2003/04/immutable.htm



Comments

Post a Comment

Popular posts from this blog

How SQL Indexes Work internally ?

Image
When an index is created, it records the location of values in a table that are associated with the column that is indexed. Entries are added to the index when new data is added to the table. When a query is executed against the database and a condition is specified on a column in the WHERE clause that is indexed, the index is first searched for the values specified in the WHERE clause. If the value is found in the index, the index returns the exact location of the searched data in the table. Figure 16.1 illustrates how an index functions. Suppose the following query was issued: SELECT *  FROM TABLE_NAME WHERE NAME = 'SMITH'; As shown in Figure 16.1, the NAME index is referenced to resolve the location of all names equal to 'SMITH'. After the location is determined, the data can be quickly retrieved from the table. The data, in this case names, is alphabetized in the index. A full table scan would occur if there were no index on the table and the same que...
Read more

UML,HLD and LLD.

UML is a standard language for specifying, visualizing, constructing, and documenting the artifacts of software systems. Here is a Complete understanding of UML.   http://www.tutorialspoint.com/uml/index.html High Level Design (HLD) is the overall system design - covering the system architecture and database design. It describes the relation between various modules and functions of the system. data flow, flow charts and data structures are covered under HLD. Low Level Design (LLD) is like detailing the HLD. It defines the actual logic for each and every component of the system. Class diagrams with all the methods and relation between classes comes under LLD. Programs specs are covered under LLD. In HLD, you design the component level abstractions and interactions. In LLD, for each component, you go to the lower level such as class and method levels, describe what each class's responsibility, its interface and its interaction with other classes. All terms like "high...
Read more