Re: [v3] Tiny project, state of v3 etc
Seth via Spirit-general <[email protected]> Tue, 02 Jul 2024 22:52:46 +0200
| Newsgroups | gmane.comp.parsers.spirit.general |
|---|---|
| Message-ID | <[email protected]> |
--===============1946212831722966804== Content-Type: multipart/alternative; boundary=11b1e2d311fe44a5b130126ca1b9563a --11b1e2d311fe44a5b130126ca1b9563a Content-Type: text/plain;charset=utf-8 Content-Transfer-Encoding: quoted-printable On Mon, Jul 1, 2024, at 4:48 PM, Michael Powell wrote: >=20 > On Sun, Jun 30, 2024 at 9:08=E2=80=AFPM Richard <[email protected]= > wrote: >>> Are you aware of Boost.Parser? If I recall correctly, it was recent= ly >>> accepted to boost and is considered (with blessings from Spirit devs) >>> as the successor to spirit: <https://github.com/tzlaine/parser> >>=20 >> Consider me aware now, appreciated. That looks interesting. Not aware= of the history at all, assuming it draws on Spirit expertise? X3?=20 I don't think it draws on experience. It's a separate project from scrat= ch. It only borrows the expression-template conventions and perhaps the = *idea* of automatic attribute propagation. This may have pros (e.g. not requiring Boost Fusion and first-class Boos= t PFR support, UTF8 by default?) and cons (not having quite the same ver= satility/battle testing). >=20 > Being honest, it is not a successor (yet). It is in proposed stage, co= rrect? What's the status with that? Also, seems as though some of the gi= thub badges (?). It is accepted, on conditions. The author will meet the conditions and t= hen it will be released in a future Boost Release. I know because I spen= t hours some time ago scouring the Boost dev mailing list for this infor= mation (why is it not on the site? God only knows). https://lists.boost.= org/Archives/boost/2024/03/256151.php --11b1e2d311fe44a5b130126ca1b9563a Content-Type: text/html;charset=utf-8 Content-Transfer-Encoding: quoted-printable <!DOCTYPE html><html><head><title></title><style type=3D"text/css">p.Mso= Normal,p.MsoNoSpacing{margin:0}</style></head><body><div>On Mon, Jul 1, = 2024, at 4:48 PM, Michael Powell wrote:<br></div><blockquote type=3D"cit= e" id=3D"qt" style=3D""><div dir=3D"ltr"><div dir=3D"ltr"><br></div><div= >On Sun, Jun 30, 2024 at 9:08=E2=80=AFPM Richard <<a href=3D"mailto:l= [email protected]" target=3D"_blank">[email protected]</a>> wr= ote:<br></div><div class=3D"qt-gmail_quote"><blockquote class=3D"qt-gmai= l_quote" style=3D"margin-top:0px;margin-right:0px;margin-bottom:0px;marg= in-left:0.8ex;border-left-width:1px;border-left-style:solid;border-left-= color:rgb(204, 204, 204);padding-left:1ex;"><div dir=3D"ltr"><div class=3D= "qt-gmail_quote"><blockquote class=3D"qt-gmail_quote" style=3D"margin-to= p:0px;margin-right:0px;margin-bottom:0px;margin-left:0.8ex;border-left-w= idth:1px;border-left-style:solid;border-left-color:rgb(204, 204, 204);pa= dding-left:1ex;"><div>Are you aware of Boost.Parser? If I recall c= orrectly, it was recently<br></div><div> accepted to boost and is consid= ered (with blessings from Spirit devs)<br></div><div> as the successor t= o spirit: <<a href=3D"https://github.com/tzlaine/parser" rel=3D"noref= errer" target=3D"_blank">https://github.com/tzlaine/parser</a>><br></= div></blockquote><div><br></div><div>Consider me aware now, appreciated.= That looks interesting. Not aware of the history at all, assuming it dr= aws on Spirit expertise? X3? <br></div></div></div></blockquote></d= iv></div></blockquote><div>I don't think it draws on experience. It's a = separate project from scratch. It only borrows the expression-template c= onventions and perhaps the *idea* of automatic attribute propagation.<br= ></div><div><br></div><div>This may have pros (e.g. not requiring Boost = Fusion and first-class Boost PFR support, UTF8 by default?) and cons (no= t having quite the same versatility/battle testing).<br></div><div><br><= /div><blockquote type=3D"cite" id=3D"qt" style=3D""><div dir=3D"ltr"><di= v class=3D"qt-gmail_quote"><div><br></div><div>Being honest, it is not a= successor (yet). It is in proposed stage, correct? What's the status wi= th that? Also, seems as though some of the github badges (?).<br></div><= /div></div></blockquote><div>It is accepted, on conditions. The author w= ill meet the conditions and then it will be released in a future Boost R= elease. I know because I spent hours some time ago scouring the Boost de= v mailing list for this information (why is it not on the site? God only= knows). <a href=3D"https://lists.boost.org/Archives/boost/2024/03/= 256151.php">https://lists.boost.org/Archives/boost/2024/03/256151.php</a= ><br></div></body></html> --11b1e2d311fe44a5b130126ca1b9563a-- --===============1946212831722966804== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============1946212831722966804== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Spirit-general mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/spirit-general --===============1946212831722966804==--