[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: RFC: c++: provide control over the stack.hh file name
From: |
Hans Åberg |
Subject: |
Re: RFC: c++: provide control over the stack.hh file name |
Date: |
Fri, 28 Sep 2018 12:46:31 +0200 |
> On 24 Sep 2018, at 22:36, Akim Demaille <address@hidden> wrote:
>
> In the case of stack.hh, I think we don’t care. In fact, I expect
> people to ‘%define api.stack.file none’ to not generate this file.
> But in the case of location.hh/position.hh, it might be important
> to generate them in foo/ast while the parser is in foo/parse.
> But then, what should the #include look like? Maybe we cannot
> just invent it, and should also introduce api.stack.include to
> specify it.
>
> Just thinking aloud. But I’d be happy to not be alone doing so :)
Since you asked for it:-), it would be safest to have all these helper classes
in the parser header, and with the same name prefix, or maybe even as
subclasses.
- Re: RFC: c++: provide control over the stack.hh file name, (continued)
- Re: RFC: c++: provide control over the stack.hh file name, Frank Heckenbach, 2018/09/28
- Re: RFC: c++: provide control over the stack.hh file name, Hans Åberg, 2018/09/28
- Re: RFC: c++: provide control over the stack.hh file name, Frank Heckenbach, 2018/09/28
- Re: RFC: c++: provide control over the stack.hh file name, Hans Åberg, 2018/09/28
- Re: RFC: c++: provide control over the stack.hh file name, Frank Heckenbach, 2018/09/28
Re: RFC: c++: provide control over the stack.hh file name, Hans Åberg, 2018/09/24
Re: RFC: c++: provide control over the stack.hh file name,
Hans Åberg <=
Re: RFC: c++: provide control over the stack.hh file name, Akim Demaille, 2018/09/30