I started with JDT because it is a maintained parser, I had some experience
of working with it, and I wanted to test JNIPort as well.
I actually did not know that the Java parser of SmaCC is maintained
actively. I will certainly look at the Java AST.
On Wed, Aug 19, 2015 at 4:36 PM, Nicolas Anquetil <nicolas.anquetil(a)inria.fr
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:
I have released SmaCC 2.0.5, aligned on the main SmaCC with a small fix
on the Java parser, a few additional parsers (Cucumber), the addition of
source code coverage of SmaCC generated parsers (with many thanks to John
Brant and Don Roberts). The project is available on github
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
(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:
Moose-dev mailing list
"Every thing has its own flow"