[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: syntax_error constructor is declared inline
From: |
Hans Åberg |
Subject: |
Re: syntax_error constructor is declared inline |
Date: |
Tue, 8 May 2018 18:11:53 +0200 |
> On 8 May 2018, at 11:13, Akim Demaille <address@hidden> wrote:
>
> I’m all rusted on Bison.
Welcome back, though!
>> I will apply this patch in my C++17 version, but since I'm not a
>> Bison maintainer, I can't promise it will go in the C++98 parser, or
>> in the official Bison sources at all. For now, you can apply the
>> patch manually (your installation directory may vary).
>
> I will try to make soon a maintenance release of Bison, with
> bug fixing and gnulib updates. Then it will be great to address
> modern C++. However, I’d prefer sticking to a single skeleton
> rather than having to maintain several (not to mention the CI
> headaches…)
That is what I thought, too. The fixes that Frank made requires only C++11 from
what I understand, except that C++17 comes in when using variants, though there
is an easy workaround to use external ones. Your idea of letting Bison to keep
track of the type does not work in mid-actions as it is needed to decide which
copy constructor to use, unlike C then.