Re: unstable number of arguments to yylex

[Akim Demaille]

 John> In a  %pure parser, the number of arguments to yylex() is dependent
 John> upon whether any @N constructs are detected. This is a problem during
 John> development when one removes or comments out certain actions that
 John> contain @N constructs. Suddenly, the compiler may produce errors about
 John> the number of arguments to yylex.

 John> Is there a concrete method to force the number of parameters to be
 John> stable -- either one or two, but not flip-flop between them?

Use %locations.