Re: boost::variant usage with boost::spirit broken in 1.68 but ok in 1.60?
SCHNEIDER Hermann <[email protected]> Fri, 9 Nov 2018 10:16:05 +0000
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <19D548AA577D1E4484AFF19CF92CD08D218AA5BD@EU-DCC-MBX03.dsone.3ds.com> |
Hi Seth, We've the following issue https://wandbox.org/permlink/rKMDr78pc6REDp0z . It's exactly this one https://github.com/boostorg/spirit/issues/321 . What I noticed: it is actually also broken in 1.60 on wandbox. It works on our 1.60 build with the actual code which uses lazy parsers everywhere. But I guess it was more like a bug that it worked for us in the first place. So, how can I fix or circumvent the problem above? Or is boost::variant and boost::fusion::vector not supported with lazy parsers? Mit freundlichen Grüßen / Best Regards / Cordialement, Hermann SCHNEIDER From: Seth <[email protected]> Sent: Thursday, November 8, 2018 23:31 To: Spirit General Mailing List <[email protected]> Subject: Re: [Spirit-general] boost::variant usage with boost::spirit broken in 1.68 but ok in 1.60? On 06-11-18 15:59, SCHNEIDER Hermann wrote: Does anyone have a clue why this worked with 1.60 but doesn't with 1.68. The change log between 1.60 and 1.68 doesn't show much related? Or does anyone know a quick workaround? https://www.boost.org/users/history/version_1_62_0.html contains significant changes to Variant interface (surrounding construction and assignment). Minor changes in https://www.boost.org/users/history/version_1_64_0.html too. Spirit received some related changes in 1.67: https://github.com/boostorg/spirit/pull/201 (and #209) This is most likely what impacts you. If you share the problem we could see it. This email and any attachments are intended solely for the use of the individual or entity to whom it is addressed and may be confidential and/or privileged. If you are not one of the named recipients or have received this email in error, (i) you should not read, disclose, or copy it, (ii) please notify sender of your receipt by reply email and delete this email and all attachments, (iii) Dassault Systèmes does not accept or assume any liability or responsibility for any use of or reliance on this email. Please be informed that your personal data are processed according to our data privacy policy as described on our website. Should you have any questions related to personal data protection, please contact 3DS Data Protection Officer at [email protected]<mailto:[email protected]> For other languages, go to https://www.3ds.com/terms/email-disclaimer _______________________________________________ Spirit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/spirit-general