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

[Hans Åberg]

> On 30 Sep 2018, at 17:47, Paul Eggert <address@hidden> wrote:
> 
> 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.

Or not generate it and issue a warning if it is already present, giving a 
chance to remove it from distributions that might have it included.