{"id":1930,"date":"2019-04-02T08:24:03","date_gmt":"2019-04-02T12:24:03","guid":{"rendered":"http:\/\/codinggorilla.com\/?p=1930"},"modified":"2019-04-03T13:25:38","modified_gmt":"2019-04-03T17:25:38","slug":"series-on-program-transformation-systems-spoon-2004","status":"publish","type":"post","link":"http:\/\/165.227.223.229\/index.php\/2019\/04\/02\/series-on-program-transformation-systems-spoon-2004\/","title":{"rendered":"Series on program transformation systems: Spoon (2005)"},"content":{"rendered":"\n

This is the next entry in the series on program transformation systems. This article describes Spoon<\/a>, a system for Java source code. It has been in development since 2005 and is actively being developed to this day.<\/p>\n\n\n\n\n\n\n\n

One part of Spoon is an API to modify the abstract syntax tree of a Java program. For example, the API has methods to add or delete classes, methods, methods, and statements. An example shown on Spoon’s website<\/a> checks for empty catch<\/em> blocks using an API for visiting tree nodes. As noted, “[t]he concept of a CtScanner<\/g> is a “visitor pattern”, which can be applied to processing<\/g> of Abstract [S]yntax [T]ree.”<\/p>\n\n\n\n

The second part of Spoon uses Java Annotations. An example they give<\/a> shows how to insert a check into the code for a null parameter check. They note that “[t]he implementation of such an annotation would not be straightforward using Java’s processing API since it would not allow us to just insert the NULL check in the body of the annotated method.” It isn’t clear to me what API they are referring to, or why Spoon’s API for modifying an AST could not be used to insert a null check.<\/p>\n\n\n\n

Observations and notes<\/h2>\n\n\n\n