Well, also because I am not yet confident about ANTLR both as a tool and of my ability to use it effectively.
The main advantage of using ANTLR is when defining the grammar - as it allows rapid prototyping. However, I am finding that some of the tools are a bit flaky. The Eclipse ANTLR IDE just doesn't seem to work; the ANTLRWorks tool can't handle backtracking in the Interpreter (one has to use the Debugger to work around this). Unfortunately it seems very hard to remove backtracking in a C like grammar - even the official ANTLR Java and C grammars rely on backtracking - so I reckon if experts can get rid of this I have no chance! I do not yet know how robust ANTLR is; so that's another concern. If I hit bugs then I would rather just handcode a parser than waste time working out why things aren't working. Already the tools mentioned above have been a fit frustrating due to the bugs/limitations. Regards Dibyendu On Sep 12, 1:52 pm, "Rodrigo B. de Oliveira" <[email protected]> wrote: > On Sun, Sep 12, 2010 at 5:35 AM, Dibyendu Majumdar > > <[email protected]> wrote: > > ... I may still write a hand coded recursive descent parser once the grammar > > has been defined. > > As a learning exercise I presume? > > Regards, > Rodrigo -- You received this message because you are subscribed to the Google Groups "JVM Languages" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/jvm-languages?hl=en.
