Hi, Thank you very much for your feedback, I'm in charge of this task and I'm about to start it. I'm not a parser expert, so I'm still studying all these frameworks (I did something with JavaCC in the past, but nothing very complex). My first impression is that JavaCC is very good for low level control of generated code, while ANTLR is much easier and clearer in the grammar syntax. Of course avoiding a new dependency is a pro for JavaCC. Anyway, writing the grammar is only a part of the job, the real challenge will be integrating the new parser with existing OrientDB code and improving all the related functions (eg. query optimization).
I will let you know about the progress of my work Regards Luigi 2014-08-09 21:28 GMT+02:00 Fidel H Viegas <[email protected]>: > > > > On Sat, Aug 9, 2014 at 6:28 PM, Curtis Ruck <[email protected]> wrote: > >> I've used antlr 3 & 4, and the changes in 4 make it extremely easy to >> use, within the scope of parsing grammars. The only benefit to javacc that >> I'm aware of is the lack of a runtime dependency, but I believe the >> flexibility during grammar development more than makes up for it since the >> antlr license is friendly. >> >> >> > I haven't played with ANTLR in a while, but I have used antlr 3 last year. > JavaCC on its own without JJTree is not as easy as SableCC or ANTLR with > regards to tree traversals. I tried to use it in a project a couple of > years ago, but dumped it over SableCC due to simplicity. It was faster than > SableCC, though. > > What are you guys using at the moment? > > Regards, > > Fidel H Viegas > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
