> -----Original Message----- > From: antlr-interest-boun...@antlr.org [mailto:antlr-interest- > boun...@antlr.org] On Behalf Of Peterson, Joe > Sent: Monday, July 13, 2009 5:06 PM > To: Gavin Lambert; antlr-inter...@antlr.org > Subject: Re: [antlr-interest] Composite grammars and "no start rule" > warning > > > If you are using another_file from other contexts (or if the above > > doesn't work), then you could try defining a throwaway rule in > > another_file.g: > > > another_start : list EOF; > > Ah, yeah, I could do this one. I remember either reading about this or > doing this before. Today, it didn't occur to me to write code that will > never be tested. My code coverage shouldn't suffer too much and I like > this better than using a single rule to call into the file every time. > It's probably better from a style point of view to call the rule something like __prevent_compiler_warnings. That makes it obvious that you're not expecting to have the rule called. Troy 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 -~----------~----~----~----~------~----~------~--~---
