aboutsummaryrefslogtreecommitdiff
path: root/deps/lombok/org.eclipse.jdt.apt.pluggable.core_1.0.200.v20090526-2130.jar
diff options
context:
space:
mode:
authorReinier Zwitserloot <reinier@tipit.to>2009-06-12 03:40:07 +0200
committerReinier Zwitserloot <reinier@tipit.to>2009-06-12 03:40:07 +0200
commite84bdd32e71b029d8d1f2fa7849e998953984f47 (patch)
treed3e7ff61b9d1b84de36b5d41496f5436d853d114 /deps/lombok/org.eclipse.jdt.apt.pluggable.core_1.0.200.v20090526-2130.jar
parent4c18c774fc60eca7e104b3eaa5535ce94ec66198 (diff)
downloadlombok-e84bdd32e71b029d8d1f2fa7849e998953984f47.tar.gz
lombok-e84bdd32e71b029d8d1f2fa7849e998953984f47.tar.bz2
lombok-e84bdd32e71b029d8d1f2fa7849e998953984f47.zip
Singularly massive code change, too hard to document. Basically, hooking now 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.
Diffstat (limited to 'deps/lombok/org.eclipse.jdt.apt.pluggable.core_1.0.200.v20090526-2130.jar')
0 files changed, 0 insertions, 0 deletions