Re: RFC: c++: provide control over the stack.hh file name

[Akim Demaille]

> Le 30 sept. 2018 à 17:47, Paul Eggert <address@hidden> a écrit :
> 
> Akim Demaille wrote:
>>    So offer the user a means to (i) decide what the name of the output
>>    file should be, and (ii) not generate this file at all (its content
>>    will be inline where the parser is defined).
> 
> Another idea would be to generate an empty stack.hh file for now (actually, a 
> file saying only "/* This file is present only to cater to obsolescent build 
> procedures that expect a stack.hh file.  */", and do this even if the user 
> does not specify any option at all. This will help warn users that eventually 
> the file will go away, something that should also be put into the 
> documentation of course.

I agree with this!
See https://lists.gnu.org/archive/html/bison-patches/2018-09/msg00151.html.

I would also be happy to get your opinion about using %require
as a means to change the default between versions.  And for
instance %require 3.2 could imply don’t generate stack.hh at
all.