Thank you, but both suggestions are not feasible for now. Changing the grammar is not in my league (at least not yet :) My knowledge here is limited to what I've learnt in college many years ago. While I agree that I have to study that, I also have to study XPath and other topics for the same project [Indeed I AM using MarpaX::Languages::SQL2003::AST and switched to XML output based on Durand's suggestion]. That's why I've stated that I would like to postpone that task for now!
Pre-process will require me to do in RegExp many of the tasks that Marpa is doing better and that was the reason that I've switched to Marpa based solution to begin with... and I am still in the begining of a long learning curve :| ZA On Tuesday, December 30, 2014 5:32:26 PM UTC-5, Ron Savage wrote: > > There are 2 ways to handle this: > > o Pre-process the input, so 'select top 5' becomes 'select'. > > o Change the grammar. > > If choosing the 2nd, I'd subclass MarpaX::Languages::SQL2003::AST and > commit myself to adding as much MS-specific code to the grammar as needed > to make the project work. The advantage is that you can get help here on > the syntax for such grammar extensions. And it's immeasurably better if 1 > module does this than if everyone tries to do it in parallel, since we all > then have access to a new custom module. > > > -- You received this message because you are subscribed to the Google Groups "marpa parser" 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.
