Hi Bart! Thanks for the quick answer! Adding an EOF to the rule solves the issue in the toy example. Unfortunately we are using custom token label types and are now getting a ClassCastException. It seems that we now have the problem mentioned here:
http://www.antlr.org/pipermail/antlr-interest/2009-November/036712.html Any thoughts on that? On 09.03.2010 15:04, Bart Kiers wrote: > Hi Chris, > > Since the input '<<<<<<< .mine' does not contain any illegal tokens, > the parser just stops parsing since (statement)* will also match > nothing. You'll want to "tell" your parser to continue parsing all the > way to the end of your token stream. Do that by adding an EOF to the > end of your entry-point: presumably the source parser rule: > > source > : (statement)* EOF > ; > > Regards, > > Bart. > -- Dipl.-Ing. Christoph Schinko c.schi...@cgv.tugraz.at Institute of Computer Graphics and Knowledge Visualization Graz University of Technology tel: +43 (316) 873-5416 Inffeldgasse 16c, 8010 Graz, Austria 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-inter...@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.
