Boost C++ Libraries: Ticket #10512: Syntax error in Regex not detected https://svn.boost.org/trac10/ticket/10512 <p> The regex "A{2" is not detected as syntactically incorrect. It matches the string "03A{2B6FC7". Other bad regexes (like "A<a class="report" href="https://svn.boost.org/trac10/report/2">{2}</a>}") raise an error correctly. </p> <p> This worked in 1.55. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/10512 Trac 1.4.3 martin.grieb@… Wed, 17 Sep 2014 15:47:26 GMT <link>https://svn.boost.org/trac10/ticket/10512#comment:1 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/10512#comment:1</guid> <description> <p> This was broken in <a class="ext-link" href="https://svn.boost.org/trac/boost/changeset/84371"><span class="icon">​</span>84371</a> . I regard this as bug, not as feature. "A}2" still raises an error as it should (but which is not consistent). </p> <p> The documentation mentions {} as special characters, the "ignore error and treat this as literal string" behavior is not documented. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>John Maddock</dc:creator> <pubDate>Thu, 25 Sep 2014 10:56:23 GMT</pubDate> <title>status changed; resolution set https://svn.boost.org/trac10/ticket/10512#comment:2 https://svn.boost.org/trac10/ticket/10512#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">wontfix</span> </li> </ul> <p> Sigh... we do what Perl does, this was changed in response to <a class="ext-link" href="https://svn.boost.org/trac/boost/ticket/8569"><span class="icon">​</span>https://svn.boost.org/trac/boost/ticket/8569</a> even though I would personally prefer this to raise an error. </p> <p> I've updated the docs, and changed trailing }'s to also be treated as literals. </p> Ticket martin.grieb@… Thu, 25 Sep 2014 11:09:19 GMT <link>https://svn.boost.org/trac10/ticket/10512#comment:3 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/10512#comment:3</guid> <description> <p> What about ECMAScript mode which is identical to Perl mode? Is the Perl behavior valid in ECMAScript mode? Would splitting ECMAScript mode from Perl mode (with different error handling as only difference) be a possible solution? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>John Maddock</dc:creator> <pubDate>Thu, 25 Sep 2014 11:20:36 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/10512#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/10512#comment:4</guid> <description> <p> To be honest we don't really support ECMAScript as such (except as a subset of Perl). It would take quite a bit of work to figure out what needs to be disabled for a "strict" ECMAScript mode. </p> </description> <category>Ticket</category> </item> </channel> </rss>