Terence Parr wrote: > nope... how can I be sure you do not want those elided constructs? > > foo -> foo > > I suppose I could get rid of, but two compilers really get rid of a=a;? OK I mis-wrote, I meant just dropping the production side. You seemed to imply that its presence slows things up.
And I think a=a; is fair game if you know that operator= has no side effects. Which is true in Java, and you can define to be true for other antlr parse tree constructs. Or have I missed something obvious? (Been a long 4 day week, somehow) James List: http://www.antlr.org:8080/mailman/listinfo/antlr-interest Unsubscribe: http://www.antlr.org:8080/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 [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/il-antlr-interest?hl=en -~----------~----~----~----~------~----~------~--~---
