Java Puzzle – For Each Loop

 

Enhanced version of for loop introduced in JDK 5.0 is for-each. Here is the simple code for traversing a list to search an item and once it finds the item , remove it from list.

  1: import java.util.*;
  2: 
  3: class NewForLoopTest 
  4: {
  5: 	public static void main(String[] args) 
  6: 	{
  7: 		ArrayList<String> list = new ArrayList<String>();
  8: 		list.add("A1");
  9: 		list.add("A2");
 10: 		list.add("A3");
 11: 		list.add("A4");
 12: 		list.add("A5");
 13: 		for(String str: list){
 14: 			if(str.equals("A2")) {
 15: 				list.remove(str);
 16: 				System.out.println("A2 found and removed");
 17: 			}
 18: 		}
 19: 		System.out.println("End of Program");
 20: 	}
 21: }

This programs look good and expecting returns list after removing the item.


But the out of this program is :


---------- java ----------
A2 found and removed
Exception in thread "main" java.util.ConcurrentModificationException
    at java.util.AbstractList$Itr.checkForComodification(AbstractList.java:372)
    at java.util.AbstractList$Itr.next(AbstractList.java:343)
    at NewForLoopTest.main(NewForLoopTest.java:13)

Output completed (0 sec consumed)

Why? Here for each loop creates implicit iterator for traversing list and when we are removing list element using list object, it suppose to give Concurrent Modification Exception.

 

 

  































Comments















Post a Comment






























Popular posts from this blog









State Design Pattern by Example




















Image







State pattern  falls under the category of Behavioral  patterns. State design pattern comes in picture when a system’s behavior is depends on its own state or some other resource’s state. If an implementation is depends on the states, we end up with snarl of conditional statement every where in code. A very neat approach to deal with such situation is to separate out every state’s behavior and use them where ever they are applicable.   The state pattern allows an object to alter its behavior when is internal state changes . The object is appeared to change its class.   State pattern is a way to implement the same.   Class Diagram :    As above class diagram shows, System class holds state instance. As state of system changes , all handle request delegated to respective State’s concrete implementation.   Example : Have an example of Vending machine. Vending machine has following states      No Coin Inserted     Coin Inserted     Dispensing     Empty    Following diagram explain behavior...








Read more










Eclipse command framework core expression: Property tester




















Image







  Addition to Eclipse command framework series, this post explains use of property tester to control command’s enable/visible properties. In earlier post we have tried declarative way to achieve same thing but property tester gives us more control.   Property tester is associated with, tester class which implements PropertyTester.java, a namespace and set of property which it supports. We can refer this property tester using its namespace + a property name. It gives you call back to test() method with property name as parameter inside property tester class. We can configure property tester for type of input parameter.   Here is sample declaration of property tester extension point     < extension          point ="org.eclipse.core.expressions.propertyTesters" >       < propertyTester             class ="com.example.advance.cmd.EditorTester"             id ="com.example.advance.cmd.propertyTester1"             namespace ="com.example.advance.cm...








Read more










Composite Design Pattern by example




















Image







This post explains Composite design pattern with an example.   When to use ?  – Use Composite pattern when you have treat a collection of objects as they were once one thing. With Composite design pattern it is very easy to simplify operations over collection data structure. It reduces complexity of the code required if you were going to handle collection as special case.   How to Use?  - The Composite pattern consist of Component, Leaf and Composite Classes as shown below class diagram   Component  – Component declares the common interface that both the single and composite nodes will implements   Leaf  – The leaf class represent the singular atomic data type implementing he component interface.           Composite  – Composite is an abstract entity which declares common functionality which are needed by concrete implementation for handling collection data.   An Example -             Item.java   public interface Item {         public double getPrice();    ...








Read more