[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 0/8] provide more control over C++ file names
|
From: |
Hans Åberg |
|
Subject: |
Re: [PATCH 0/8] provide more control over C++ file names |
|
Date: |
Sun, 7 Oct 2018 15:14:28 +0200 |
> On 6 Oct 2018, at 18:03, Akim Demaille <address@hidden> wrote:
>
> I think I have finally reached a point where I have implemented
> everything I had on my mind about the names of the auxiliary files in
> C++. If I had known earlier what a burden it is, I guess I would have
> hesitated more... But I really wanted two C++ parsers to be able to
> export and use a single location.hh file.
It might be in its own namespace with a Bison version number in it. Then if it
is present, Bison only updates it if versions differ. This avoids unneeded file
dependency recompilation.
- [PATCH 0/8] provide more control over C++ file names, Akim Demaille, 2018/10/06
- [PATCH 7/8] c++: provide a means to control how location.hh is included, Akim Demaille, 2018/10/06
- [PATCH 8/8] NEWS: document api.*.file changes, Akim Demaille, 2018/10/06
- [PATCH 6/8] c++: support absolute api.location.file names, Akim Demaille, 2018/10/06
- [PATCH 3/8] c++: make stack.hh completely useless, Akim Demaille, 2018/10/06
- [PATCH 5/8] c++: when api.location.file is defined, don't generate stack.hh, Akim Demaille, 2018/10/06
- [PATCH 4/8] c++: make position.hh completely useless, Akim Demaille, 2018/10/06
- [PATCH 2/8] c++: add support for api.position.file and api.location.file, Akim Demaille, 2018/10/06
- [PATCH 1/8] c++: provide control over the stack.hh file name, Akim Demaille, 2018/10/06
- Re: [PATCH 0/8] provide more control over C++ file names,
Hans Åberg <=