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

[Hans Åberg]

> On 24 Sep 2018, at 22:36, Akim Demaille <address@hidden> wrote:
> 
> It was really stupid to generate stack.hh: it’s absolutely useless
> except in the parser itself.
> 
> It’s different in the case of location.hh and position.hh.  I have
> several parsers that generate ASTs tagged with source locations,
> using Bison’s generated location.hh and position.hh, so I really
> want to be able to use these files independently of the parser’s
> foo.tab.hh.

The problem is what happens using multiple parsers: If they are in different 
namespaces, then there should be in different headers. If they are in the same 
namespaces, then the header will be overwritten when compiling the different 
parsers which will affect compilation dependency.