Hi Jim! Thanks for your replies!!
The input lines are of the form "var = data" so they are pretty simple! If I got this right, you suggest using something like a body_set : body_start (probably a "greedy" option here?) body_end rule and then just add code to parse the intermediate lines (which are pretty simple) manually?? Thanks! Nikos On Tue, Apr 21, 2009 at 3:31 PM, Jim Idle <j...@temporal-wave.com> wrote: > Nick Vlassopoulos wrote: > > Hi Andreas, > > > > Thanks for your fast reply! > > So it should be something like a "line parser" that's instatiated for > > each line of the BODY section! > > > No - you don't want to do this really, you will create millions of > malloc/free calls - go with the custom input stream I mentioned and you > will be fine. It sounds like you can easily pick out the faked EOF > points without parsing them. > > What is the input? If it is just millions of data elements, then you > could parse the headers, then have the input stream traverse the data > points with a little custom code, until the next header is seen. > > Jim > > List: http://www.antlr.org/mailman/listinfo/antlr-interest > Unsubscribe: > http://www.antlr.org/mailman/options/antlr-interest/your-email-address > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "il-antlr-interest" group. To post to this group, send email to il-antlr-interest@googlegroups.com To unsubscribe from this group, send email to il-antlr-interest+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en -~----------~----~----~----~------~----~------~--~---
List: http://www.antlr.org/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org/mailman/options/antlr-interest/your-email-address
