Boost C++ Libraries: Ticket #10752: Fusion limit is not mentioned in Spirit documentation https://svn.boost.org/trac10/ticket/10752 <p> In <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/10746" title="#10746: Bugs: Compiler error for valid boost::spirit::qi grammar (closed: invalid)">#10746</a> I revealed a limit in boost::fusion that is not mentioned in the documentation of boost::spirit. </p> <p> The documentation of boost::spirit should mention such limits (and perhaps also offer workarounds in its example code) </p> <p> And – because my example code in <a class="closed ticket" href="https://svn.boost.org/trac10/ticket/10746" title="#10746: Bugs: Compiler error for valid boost::spirit::qi grammar (closed: invalid)">#10746</a> also considered as "bad style" due to the use of semantic actions in the parser – it would be very nice if there is either a parser for uuids (and other boost data types) in boost::spirit or at least an example that shows how to write such parsers in a better style. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10752 Trac 1.4.3 Nikita Kniazev <nok.raven@…> Wed, 21 Feb 2018 23:32:41 GMT <link>https://svn.boost.org/trac10/ticket/10752#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/10752#comment:1</guid> <description> <p> The downside of putting it on the docs -- most of users don't read them and just googles the error message. I added a static assert to Fusion <a class="ext-link" href="https://github.com/boostorg/fusion/pull/168"><span class="icon">​</span>https://github.com/boostorg/fusion/pull/168</a> as I think it is a better way to deal with the problem. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Joel de Guzman</dc:creator> <pubDate>Thu, 15 Mar 2018 22:58:19 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/10752#comment:2 https://svn.boost.org/trac10/ticket/10752#comment:2 <ul> <li><strong>status</strong> <span class="trac-field-old">new</span> → <span class="trac-field-new">closed</span> </li> <li><strong>resolution</strong> → <span class="trac-field-new">fixed</span> </li> </ul> Ticket