[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [OT] Help with bisonc++(1)
From: |
Hans Åberg |
Subject: |
Re: [OT] Help with bisonc++(1) |
Date: |
Mon, 31 Jul 2017 10:04:22 +0200 |
> On 31 Jul 2017, at 05:38, Kip Warner <address@hidden> wrote:
>
> On Sat, 2017-07-29 at 00:43 +0200, Hans Åberg wrote:
>> The untyped C++ parser is fine, as far as I know. There is a calc++
>> example in the distribution which shows how to use locations for
>> error reporting. The typed one may have a problem with the variants,
>> but perhaps that can be fixed with std::variant of C++17, the latter
>> which GCC supports, though there seems to be no developer right now.
>
> Thanks Hans, but I reckon I'm too far down the bisonc++(1) rabbit hole
> now.
As this is the list for Bison, you are not likely to get much help here. You
may try the Usenet newsgroup comp.compilers.
> warning: base class ‘class Meta__::Base’ should be explicitly
> initialized in the copy constructor [-Wextra]
>
> I can of course suppress this warning, but I'd rather not. What I don't
> understand is what the warning concerns since the Base class
> Semantic<tg_> derives from only has a default constructor:
> private:
> virtual Base *vClone() const = 0;
> virtual void *vData() const = 0;
> };
It may have something to with that it it is abstract. Bison C++ uses for stack
std::deque, so copy constructors are not invoked.