Mailing-List: contact notifications-help@groovy.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@groovy.apache.org
From: mariogarcia <git@git.apache.org>
To: notifications@groovy.apache.org
Reply-To: notifications@groovy.apache.org
References: <git-pr-439-groovy@git.apache.org>
In-Reply-To: <git-pr-439-groovy@git.apache.org>
Subject: [GitHub] groovy pull request #439: WIP Add groovy-macro docs
Content-Type: text/plain
Message-Id: <20161009135332.43374DFB78@git1-us-west.apache.org>
Date: Sun,  9 Oct 2016 13:53:32 +0000 (UTC)
archived-at: Sun, 09 Oct 2016 13:53:34 -0000

Github user mariogarcia commented on a diff in the pull request:

    https://github.com/apache/groovy/pull/439#discussion_r82522775
  
    --- Diff: src/spec/doc/core-metaprogramming.adoc ---
    @@ -2829,6 +2829,153 @@ to use the Groovy Console, in particular the AST browser tool, to gain knowledge
     resource for learning is the https://github.com/apache/groovy/tree/master/src/test/org/codehaus/groovy/ast/builder[AST Builder]
     test suite.
     
    +==== Macros
    +
    +===== Introduction
    +
    +Until version 2.5.0, when developing AST transformations, developers should have a deep knowledge about how the AST
    +(Abstract source tree) was built by the compiler in order to know how to add new expressions or statements during
    +compile time.
    +
    +Although the use of `org.codehaus.groovy.ast.tool.GeneralUtils` static methods could mitigate the burden of creating
    +expressions and statements, it's still a low-level way of writing those AST nodes directly.
    +We needed something to abstract us from writing the AST directly and that's exactly what Groovy macros were made for.
    +They allow you to add code during compile time directly, without having translate the code you had in mind to the
    --- End diff --
    
    :+1: 


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---