aboutsummaryrefslogtreecommitdiff
path: root/src/lombok/eclipse/EclipseASTVisitor.java
AgeCommit message (Collapse)Author
2009-06-15Switched the level of the Node object you get during a visitAnnotationOnX ↵Reinier Zwitserloot
call from the Field/Type/Method/Local to the Annotation, so that you can interact with its handled flag.
2009-06-15Added annotations as definitive children of nodes in our custom AST, and ↵Reinier Zwitserloot
updated the visitor to call a separate visitAnnotationOnX method for annotated stuff. This way, 'handled' can be set per annotation. Also fixed a bug in AST generation that caused StackOverflowErrors on most source files, and did some cosmetic renaming of parameters.
2009-06-15all eclipse AST Statements objects are now part of the custom AST we build ↵Reinier Zwitserloot
for lombok. This way something like @AutoClose on a local var declaration can walk up one node, find all mentions of the variable, and add a close call right after the last mention.
2009-06-12Singularly massive code change, too hard to document. Basically, hooking now ↵Reinier Zwitserloot
occurs in the two most sane places: - After the parser is done building a first rendition of the AST. (Usually lightweight and missing method bodies etc) - After the parser is done taking such a lightweight AST and filling in the gaps. Lombok then builts its own bidirectional and somewhat saner AST out of this, and hands this saner AST off for treatment. Things in the AST can be marked as 'handled'. This seems to work swimmingly and should allow us to easily identify the annotations that are for us, and work our magic, no matter where they appear or on what, including stuff inside method bodies.