Re: [Boost-users] Possible Boost.Variant issue with JSON AST

Subject: Re: [Boost-users] Possible Boost.Variant issue with JSON AST
From: Michael Powell (mwpowellhtx_at_[hidden])
Date: 2019-01-11 02:17:35

On Thu, Jan 10, 2019 at 6:36 PM Michael Powell <mwpowellhtx_at_[hidden]> wrote:
>
> On Thu, Jan 10, 2019 at 6:15 PM Gavin Lambert via Boost-users
> <boost-users_at_[hidden]> wrote:
> >
> > On 11/01/2019 07:36, Michael Powell wrote:
> > > Here's my attempt at a flattened single source example:
> > >
> > > https://wandbox.org/permlink/83c3VXZ4W1DHoEBc
> >
> > The problems in that code are that you're using completely the wrong types.
>
> Fair observations. I've updated a bit, which I think is now tracking
> with my local progress. Chiefly now, issues with "incompatible
> skipper"?
>
> https://wandbox.org/permlink/4spQR8yXweIcVfdB

I think I got it sorted pending testing, although I am unclear why a
couple of the rules skippers' should not be specified.

> Perhaps a repeated tuple issue of some sort? Otherwise, I'm not sure I
> see what's going on there...
>
> I'd also tried forward declared structs to capture Member, Object,
> Array, etc, but this was running into Boost.Variant incomplete type
> issues.
>
> > In key_t, you're inheriting the base_type copy-constructor and
> > copy-assignment, and then creating new shadowing constructors and
> > assignment operators for the base_type (note: these are *not* a
> > copy-constructor nor copy-assignment operator for key_t itself!).
> >
> > In numeric_t(const sign_type& other), you're getting compile errors
> > because you probably intended to use numeric_t instead of sign_type as
> > the parameter.
> > _______________________________________________
> > Boost-users mailing list
> > Boost-users_at_[hidden]
> > https://lists.boost.org/mailman/listinfo.cgi/boost-users