[Top][All Lists]

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

Re: [PATCH] Factor %FLAG at scan level.

From: Akim Demaille
Subject: Re: [PATCH] Factor %FLAG at scan level.
Date: Fri, 10 Apr 2009 17:08:57 +0200

Le 9 avr. 09 à 07:10, Joel E. Denny a écrit :

Instead of allowing the user to disable the warning globally, I think Bison can provide a more careful and flexible solution. Bison would warn
if --define contradicts %define, but Bison would not warn if
--force-define contradicts %define.

I don't like the explosion of the number of options.

It's just one new option:


And it would be straight-forward to implement.

I guess I was confuses by references to %defines in the quoted thread, and I read "defines" in your suggestion. Which makes no sense since there is NAME in the argument, but I guess I was too tired to notice.

So, in short, yes, sure!  :)

That in the end the question is: should the interface be tailored for
experienced users, or novices. Both opinions are perfectly defendable, but we need to make our mind once on this regard, and be consistent afterwards.

I'm surprised to see you argue this way after you recently supported the
"misleading reference" concept for Alex's value names.

ISTR that there was one message with which I did not agree :( But I don't have the thread here.

I'm a novice in many ways. I usually find that careful warnings save me
more frustration than they cause.

Fine with me :)

reply via email to

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