anchor.diff:  This feature is used in numerous places within the Groovy codebase for testing purposes.
   Various code snippets are compiled using both Java and Groovy to ensure the compiler is behaving as intended.
   We also use this feature to provide a productivity enhancement for polyglot developers allowing
  -Java code to be run (as Java) within the Groovy Console:
  +Java code to be compiled and/or run (as Java) from within the Groovy Console:
   
   image:img/groovyconsole_run_as_java.png[image] +
   
  
positive.code: 
  Note that while our `PointList` class has numerous list methods available
  (`size`, `contains`, `forEach`, `stream`, etc.) courtesy of Groovy's `@Delegate` transform,
  these are baked into the class file, not calling into any Groovy library or runtime code.
  
  When run, the following output is produced:
  
  
negative.code: }
  --------------------------------------
  
  We can compile those classes using `groovyc` in the normal way
  and should see the expected _Point.class_ and _PointList.class_ files produced.
  
  We can then compile the following Java code.
  We do not need the Groovy jars available for `javac` or `java`,
  we only need the class files produced from the previous step.
  