More comments, and the ANTLR code is too complex Mark H Weaver (29 May 2013 07:04 UTC)
Re: More comments, and the ANTLR code is too complex David A. Wheeler (29 May 2013 17:39 UTC)
Re: More comments, and the ANTLR code is too complex David A. Wheeler (31 May 2013 17:03 UTC)
Re: More comments, and the ANTLR code is too complex David A. Wheeler (01 Jun 2013 02:27 UTC)
Re: More comments, and the ANTLR code is too complex David A. Wheeler (10 Jun 2013 00:21 UTC)
Re: More comments, and the ANTLR code is too complex Alan Manuel Gloria (10 Jun 2013 02:01 UTC)
Re: More comments, and the ANTLR code is too complex David A. Wheeler (12 Jun 2013 00:25 UTC)
Re: More comments, and the ANTLR code is too complex Mark H Weaver (12 Jun 2013 20:13 UTC)

Re: More comments, and the ANTLR code is too complex David A. Wheeler 12 Jun 2013 00:25 UTC

Alan Manuel Gloria:
> It *might*.  I suggest we need better names.  We don't really need to
> prefix with "it_expr", for example.  So maybe "normal_it_expr" and
> "special_it_expr" instead.

Good names are always a good idea!
I've switched to those names; if anyone has an even better
idea, please speak up.

> Having more rules helps in discussing rules,

Sure!

> and may help suggest how
> to organize a top-down recursive descent parser.

The current structure is specially rigged to be especially easy
to implement as a recursive descent parser.  But if it's too hard to follow,
it's not a good idea; *people* need to understand it too :-).

> However, we might want to ask Mark H. Weaver directly if this helps
> clarify the BNF.

Agreed.

Mark H. Weaver - would splitting it up into more-but-smaller rules help?

--- David A. Wheeler