Re: RFC: variable parse.error

[Akim Demaille]

Le 23 juin 09 à 22:22, Akim Demaille a écrit :

> I am still slowly trying to normalize the name of the variables we  
> will use in Bison 2.6.  This patch deprecates %error-verbose in  
> favor of %define parse.error "verbose".
>
> I think "parse.error" is ok, but I'd be happy to receive other  
> proposals.  I am less satisfied with "simple" and "verbose".   
> "simple" is ok, but it could be "constant" for instance.  Or "yacc"  
> for that matter (actually I don't know if POSIX mandates the format  
> of the error message).
>
> "verbose" is not too good, as it is very vague, and can easily  
> denote many other strategies for error-messages.  What will we put  
> if some day we allow the user to hook the generation of error  
> messages (for instance to specify how to display the "unexpected"  
> token)?
>
> I have pushed this as "candidates/parse.error".

I have pushed the following in master, and removed this candidate  
branch.

0001-variables-parse.error.txt
Description: Text document