Ben + Josh, is this an accurate summary of your viewpoints: Java doesn't have true closures because of the "final" variable requirement and that any mutability of "closed" variables from the outer environment requires a level of indirection.
That's a logically consistent argument, although it's real language lawyer, splitting hairs argument. I'd still say that the language level limitations that are holding Java back from a more functional programming style isn't the "final" variable restriction of Closure like functionality, but the lack of first class functions and a more concise anonymous function syntax. And, ideally, Java would have a standard collections library with persistent immutability support (like Scala's collections). -- You received this message because you are subscribed to the Google Groups "The Java Posse" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/javaposse?hl=en.
