what is the status of the java parser?
Why is it not used for the new Moose parser that Doru announced (instead of building a bridge with FFI)?
is it because of name resolution (that JDT performs)?


On 19/08/2015 16:30, Thierry Goubier wrote:
Hi All,

I have released SmaCC 2.0.5, aligned on the main SmaCC[1] with a small fix on the Java parser, a few additional parsers (Cucumber), the addition of the Javascript parser, and continuous improvements on the performance and source code coverage of SmaCC generated parsers (with many thanks to John Brant and Don Roberts). The project is available on github[2]

[1] http://www.refactoryworkers.com/SmaCC.html

[2] https://github.com/ThierryGoubier/SmaCC

This release is targeted at Pharo4. All parsers should work on Pharo 5, but the GUI doesn't work. Most parsers come with full AST generation and a dedicated visitor for each, and support for native language refactoring.

To retrieve a specific parser, please use Metacello with the following script:

Metacello new
  baseline: 'SmaCC';
  repository: 'github://ThierryGoubier/SmaCC:v2.0.5';
  load: 'SmaCC-Javascript'

(SmaCC-Python, SmaCC-Java, SmaCC-Cucumber, etc...)

On Pharo4 only, to retrieve the full set (gui and tests), please use Metacello with the following expressions:

Metacello new
  baseline: 'SmaCC';
  repository: 'github://ThierryGoubier/SmaCC:v2.0.5';



Moose-dev mailing list