[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RFC: variable parse.error

From: Akim Demaille
Subject: Re: RFC: variable parse.error
Date: Fri, 24 Jul 2009 17:07:08 +0200

Le 16 juil. 09 à 11:19, Joel E. Denny a écrit :

Hi Akim.  Sorry to be so late replying.

On Tue, 23 Jun 2009, Akim Demaille wrote:

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.

How about parse.error.messages or parse.error-messages? One day we might have, for example, parse.error.recovery to specify the recovery mechanism.

Good with me.  I will work on it.

Are you thinking there will be multiple properties that can be configured

 %define parse.error.messages.token "hide"
 %define parse.error.messages.token "show"
 %define parse.error.messages.value "hide"
 %define parse.error.messages.value "show"

I don't know yet, but I rather expected the user code to be in charge of what's to be displayed. Of course in the end it means to provide yyerror with more values, so more %define options, yet I think several %define bits to binary-or might be overkill. That's just guts feeling, I have not looked into the details yet.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]