From 527b992a074c1c65727bc52c820d40340f074a6b Mon Sep 17 00:00:00 2001 From: Reinier Zwitserloot Date: Mon, 6 Jul 2009 05:48:42 +0200 Subject: Last massive documentation dump. All basic javadoc is now done, though especially the docs on the lombok annotations in the lombok package need far more massaging. Also added a feature to HandleSynchronized to not auto-generate the locker fields if a specific name is provided (because, imagine you typoed those. You'd never find it!) --- .../lombok/eclipse/agent/EclipseParserTransformer.java | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'src_eclipseagent/lombok/eclipse/agent/EclipseParserTransformer.java') diff --git a/src_eclipseagent/lombok/eclipse/agent/EclipseParserTransformer.java b/src_eclipseagent/lombok/eclipse/agent/EclipseParserTransformer.java index 66f515bf..639573e4 100644 --- a/src_eclipseagent/lombok/eclipse/agent/EclipseParserTransformer.java +++ b/src_eclipseagent/lombok/eclipse/agent/EclipseParserTransformer.java @@ -48,9 +48,11 @@ import org.objectweb.asm.Opcodes; * 2-step parsing system, where the bodies of methods aren't filled in until its actually neccessary. Lombok * gets a chance to change the AST immediately after either step. *
  • The parse(MethodDeclaration, CUD), parse(ConstructorDeclaration, CUD) and - * parse(Initializer, TypeDeclaration, CUD) methods could all be theoretically called to - * flesh out just one part of a half-finished AST tree. These methods are all instrumented to call Lombok - * with the CUD before returning it to whomever wanted it filled out.
    • + * parse(Initializer, TypeDeclaration, CUD) methods are all instrumented to not attempt to + * complete parsing a method generated by lombok, as the source positions are obviously all wrong + * (the method content isn't in the source file!) - lombok has already filled in the complete AST. + * + * Bit24 on the flags field on all ASTNode objects is used as a marker. */ class EclipseParserTransformer { private static final String COMPILER_PKG = -- cgit