Thanks for the positive comments! I've worked on the performance side of things in version 1.5, so the tokenizer is now much improved in many cases. But there is now also support for reusing the same parser for several input streams, which will reduce the amount of processing required to analyze the grammar itself (which is otherwise done once for each parsing session).
If you want to further improve the speed, I think the right place might be to optimize your Analyzer subclass to avoid creating full parse trees (if those are large). But such speed optimizations must be done on a case-by-case basis depending on your needs. Cheers, /Per On Fri, Jul 10, 2009 at 00:42, EUGENE CILOCI<ecil...@rogers.com> wrote: > Hi Per, > > Just wanted to say thanks for this great project. I'm using it to do the > parsing for my expression evaluator library (http://www.codeplex.com/Flee). > Grammatica works great, is simple to use, and I've yet to hit a parser > related bug. > > The only thing that's not ideal is the parsing speed but this is a general > parser so it's expected that it won't be as fast as a hand-coded one. Let > me know if you have any suggestions on how to improve it. > > Thanks again. > > Eugene > > _______________________________________________ > Grammatica-users mailing list > Grammatica-users@nongnu.org > http://lists.nongnu.org/mailman/listinfo/grammatica-users > > _______________________________________________ Grammatica-users mailing list Grammatica-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/grammatica-users
