> If they ever want to replace the fork/join framework with a non-recursive, > general-purpose engine then they will have to refactor all the code that > uses the recursion technique. It’s not like putting a Chevy engine in a > Ford. It will be a monster undertaking. >
Looking at Generics, raw types, primitives vs. wrappers, implicit widening conversions, constant inlining, inner classes, bridge methods, etc. I'm pretty sure that it is rather unlikely that they will touch that or anything else in any substantial way as soon as it is out of the door. Java is a pragmatic language. Fixing broken stuff is for academics. -- You received this message because you are subscribed to the Google Groups "Java Posse" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/javaposse?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
