Re: --yacc and token #define's

[Joel E. Denny]

On Sat, 10 Jun 2006, Joel E. Denny wrote:

> On Sat, 10 Jun 2006, Akim Demaille wrote:
> 
> > I'm in favor of keeping --yacc as a simple flag, not an option with
> > suboptions.
> 
> I'm seeing it your way these days.  All or nothing Yacc support is easier 
> for us, and I'm guessing there aren't any users who really need some 
> strange mix.

I should probably clarify this.  `All or nothing Yacc support' does not 
and would not accurately describe Bison's behavior.  That is, Bison lets 
you do many non-Yacc things (such as %glr-parser) when you specify --yacc.  
I don't mean to express any opinions on that behavior.

I simply mean to agree that we should not feel obligated to support 
fine-grained selection of Yacc features (specifically, --yacc suboptions) 
where it would produce more work for us and where it's probably not needed 
anyway.

Joel