Sorry i should have added some context, Team Lombok complained in the podcast that each of the major IDEs use different compilers and ASTs to represent compiled classes. Because Lombok enhances classes when they are compiled by the IDE, it is thus necssary for Lombok to analyze the AST of each and every "compiled" class. Hopefully my understanding is not wrong, but each IDE requires different haxors and the they eventually get at the AST, do their enhancements and update. The problem is because they support numerous "features" they need to repeat this exercise for each and every different AST which means thirce the work to support a single feature in order to make it work across Eclipse, JavaC and IDEA. The original idea inthe podcast was to have a "Universal AST" that would be built from any of the three ASTS. Lombok would then enchnace that and then export back to the appropriate AST.
Regarding a Universal AST to represent the Universe - im not sure how that work given any AST representation would require additional matter the represent the existing universe. I wonder if it becomes recursive as one then needs to model the AST itself which is of course not possible due to insufficient matter. Im not sure but maybe a static typing here is a bad thing as it means significant amounts of matter are required to hold all those types. This might be a vote against static typing but i dont really know. -- 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.
