Hi Akim! On Mon, Aug 1, 2022, at 1:46 AM, Akim Demaille wrote:
> However I can understand that when you add -Smyskeletons/lalr1.cc, then > you want lalr1.cc to be free to depend on other files in myskeletons/. That's exactly it. > However, instead of hard-coding this automatic -I on the base name of > -S, I would rather truly introduce -I and let the user decide what to > use. That would be great! > Are you using a regular lalr1.cc but a tuned c++.m4? > I'm not sure I want to support that: Bison's lalr1.cc wants its own c++.m4, > etc. Understood. Custom lalr1.cc also, so locally relativizing the lalr1.cc sub-includes, for example, would be totally fine if you prefer to keep them explicit for the regular version. Although in practice I would hope to converge my c++.m4 back to your standard; in fact the only thing significant was discussed on the mailing list in April and is now at https://github.com/akimd/bison/pull/85 for your comments. And I'm similarly raising my other patches; hopefully there's a way to make them consistent with your overall design, useful for everyone and reduce my need for custom skeleton at all. Many thanks! Anthony