On Wed, Nov 16, 2011 at 2:39 PM, Bart Kiers <bki...@gmail.com> wrote:
> On Wed, Nov 16, 2011 at 8:38 PM, Bart Kiers <bki...@gmail.com> wrote: > >> Hi, >> >> On Wed, Nov 16, 2011 at 8:21 PM, Jarrod Roberson >> <jar...@vertigrated.com>wrote: >> >>> >>> actually thanks to Bart I need the FLOAT rule as a parser rule with the >>> predicate because I want to be able to match >> >> >> But John raises a valid point that I didn't mention: by "promoting" such >> a rule to a parser rule, you run the risk that the parser matches a >> `number` rule for the input source: "123 . 5" (spaces around the '.') >> because the parser ignores the white spaces. >> > > Or even the input: "123 /* some comments */ . /* more comments */ 5" would > be a valid `number`... :) > Is there a way to support both a -> 1. b -> 1.1. in a pure lexer rule then, I didn't think there was? -- Jarrod Roberson 678.551.2852 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.
