Why is declaration of the variable required inside a for-each loop in java

by

This is a good question and I would be happy to see some in-depth answer. However, the official documentation says:

These shortcomings were known by the
designers, who made a conscious
decision to go with a clean, simple
construct that would cover the great
majority of cases.

The great majority of cases is the answer for me.

On a side note, personally, I think that foreach loop in Java is just a nice syntax for a standard iterator loop. So, the compiler creates the iterator for the structure and uses the variable to get the value for current iteration. To ensure that the variable has been initialised you need to declare it for the scope of loop (and I think this prevents the variable from being used somewhere else, e.g. in another thread). Because of that, you cannot use the variable after the loop. But, this is just my opinion and I would be very happy to hear from someone who knows it better. 🙂

Edit Here is an interesting article about foreach loops in Java.

Another edit I analysed (with jclasslib the bytecode of these methods:

 private static void testForEach(ArrayList<String> als) {
  for(String s: als)
    System.out.println(s);
 }

 private static void testIterator(ArrayList<String> als) {
  for(Iterator<String> is = als.iterator(); is.hasNext();) {
   String s = is.next();
   System.out.println(s);
  } 
 }

Both methods are represented by the same bytecode:

 0 aload_0
 1 invokevirtual #2 <java/util/ArrayList.iterator>
 4 astore_1
 5 aload_1
 6 invokeinterface #3 <java/util/Iterator.hasNext> count 1
11 ifeq 34 (+23)
14 aload_1
15 invokeinterface #4 <java/util/Iterator.next> count 1
20 checkcast #5 <java/lang/String>
23 astore_2
24 getstatic #6 <java/lang/System.out>
27 aload_2
28 invokevirtual #7 <java/io/PrintStream.println>
31 goto 5 (-26)
34 return

The difference is in line 1, the latter method uses invokevirtual #8. However, both invocations result in calling the same method of Iterator. So, it seems that foreach is nothing more than a syntactic sugar that the compiler just translates into a predefined construct, just as the documentation says. This does not answer the question why it is the way it is. I though this is just interesting and might be worth to know, in the context of the discussion.

More Related Contents:

  1. Java for loop syntax: “for (T obj : objects)”
  2. How does the Java ‘for each’ loop work?
  3. What is the Java ?: operator called and what does it do?
  4. Calling remove in foreach loop in Java [duplicate]
  5. Is there a difference between x++ and ++x in java?
  6. Difference between >>> and >>
  7. Why am I not getting a java.util.ConcurrentModificationException in this example?
  8. Why is “extends T” allowed but not “implements T”?
  9. Break or return from Java 8 stream forEach?
  10. Is there a difference between single and double quotes in Java?
  11. WITH statement in Java
  12. Is it possible to make anonymous inner classes in Java static?
  13. Java “?” Operator for checking null – What is it? (Not Ternary!)
  14. forEach vs forEachOrdered in Java 8 Stream
  15. Any Java libraries out there that validate SQL syntax? [closed]
  16. Modifier Keyword order in Java
  17. How does the enhanced for statement work for arrays, and how to get an iterator for an array?
  18. Why is this Java code in curly braces ({}) outside of a method?
  19. XML syntax validation in Java [closed]
  20. why is the enhanced for loop more efficient than the normal for loop
  21. The difference between += and =+
  22. What’s the difference between this and Activity.this
  23. How to Iterate through HashMap in MyBatis foreach?
  24. For-each vs Iterator. Which will be the better option
  25. Idiomatic way to use for-each loop given an iterator?
  26. How to read from files with Files.lines(…).forEach(…)?
  27. Static method invocation
  28. Nested if-else behaviour without braces
  29. What is the difference between += and =+?
  30. Is there a goto statement in Java?

Leave a Comment