Re: incorrect yychar for unambiguous GLR

[Paul Hilfinger]

 > 1. I've documented the use of YYEOF, yylval, and yylloc in semantic 
 > actions.  Was this intentionally omitted before?  Why?

Nah, just never got around to it, I guess.

 > +During deterministic @acronym{GLR} operation, the effect of @code{YYERROR} 
 > is
 > +similar to its effect in an @acronym{LALR}(1) parser.

It would be better to say "the same as" or "identical to" rather than
"similar to", because any deviations are unintentional (i.e., bugs).

 > +In a deferred semantic action, its effect is currently not well tested.
 > address@hidden The effect is probably a syntax error at the split point.
 > +

Let's say instead 

   In a deferred semantic action, its effect is undefined.

 > +Note that it is also possible to access the semantic value of the look-ahead
 > +token, if any, from a semantic action.
 > +This semantic value is stored in @code{yylval}.

OK, call me picky, but I *REALLY* dislike the phrase "note that", and
would prefer

   Within a semantic action, the semantic value of the look-ahead
   token, if any, is available in @code{yylval}.


 > +Note that it is also possible to access the location of the look-ahead 
 > token,
 > +if any, from a semantic action.
 > +This location is stored in @code{yylloc}.

Likewise,

   Within a semantic action, the location of the look-ahead
   token, if any, is available in @code{yylloc}.