Re: api.header.include and backward-compatible .y files

The upstream Raptor project has revived itself recently. Just today I
pulled in your PR and tried to sync up with upstream (which also had
it); bringing back Bison 3.0 support turned out to not be that hard on
top of that.

On 9/26/20, Akim Demaille <[email protected]> wrote:
> Hi Adam,
>
>> Le 24 sept. 2020 à 07:11, Akim Demaille <[email protected]> a écrit :
>>
>> Hi Adam,
>>
>> I'm sorry I forgot the thread was actually about a problem you
>> reported.  So let's go back to exactly that: you have a problem to
>> solve.  Give me some time to look at what you are doing in your
>> package, and I'll come back with proposals.
>
> Well, I did make a PR a couple of days ago,
> https://github.com/vgteam/raptor/pull/4, but so far received no feedback.
> Since you are post processing the generated files, of course you are way
> more dependent on the exact spelling of the generated file, which is not
> guaranteed.
>
> However, I'm quite confused.  Am I to understand that your project is not
> the upstream one? It appears that yours is forked from
> https://github.com/dajobe/raptor, and it is my understanding that they
> already moved to Bison 3.4+
> (https://github.com/dajobe/raptor/commit/70c87619ee9ca7d037720b7bd1b9652c098d7a5e).
>
> Cheers!