Boost C++ Libraries: Ticket #8278: BOOST_ASSERT_MSG prerocessed out if NDEBUG is defined regardless of BOOST_ENABLE_ASSERT_HANDLER https://svn.boost.org/trac10/ticket/8278 <p> There is an inconsistency in boost/assert.hpp. The macros <code>BOOST_ASSERT</code> and <code>BOOST_VERIFY</code> are *not* preprocessed out when <code>BOOST_ENABLE_ASSERT_HANDLER</code> is defined, but <code>BOOST_ASSERT_MSG</code> is. The inconsistency should be resolved one way or the other, and I think making <code>BOOST_ASSERT_MSG</code> behave like the other two makes the most sense. </p> <p> Assigning to you, Peter, since you created this file. Please reassign as appropriate. </p> en-us Boost C++ Libraries /htdocs/site/boost.png https://svn.boost.org/trac10/ticket/8278 Trac 1.4.3 Peter Dimov Tue, 12 Mar 2013 08:06:09 GMT owner changed https://svn.boost.org/trac10/ticket/8278#comment:1 https://svn.boost.org/trac10/ticket/8278#comment:1 <ul> <li><strong>owner</strong> changed from <span class="trac-author">Peter Dimov</span> to <span class="trac-author">Beman Dawes</span> </li> </ul> <p> I think that Beman added the _MSG variants. I agree that ASSERT_MSG should follow ASSERT. </p> Ticket viboes Thu, 14 Mar 2013 17:50:02 GMT status changed; resolution set https://svn.boost.org/trac10/ticket/8278#comment:2 https://svn.boost.org/trac10/ticket/8278#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">duplicate</span> </li> </ul> <p> duplicated of <a class="reopened ticket" href="https://svn.boost.org/trac10/ticket/7028" title="#7028: Feature Requests: NDEBUG should disable asserts even if BOOST_ENABLE_ASSERT_HANDLER is ... (reopened)">#7028</a> </p> Ticket Eric Niebler Thu, 14 Mar 2013 20:29:47 GMT status changed; resolution deleted https://svn.boost.org/trac10/ticket/8278#comment:3 https://svn.boost.org/trac10/ticket/8278#comment:3 <ul> <li><strong>status</strong> <span class="trac-field-old">closed</span> → <span class="trac-field-new">reopened</span> </li> <li><strong>resolution</strong> <span class="trac-field-deleted">duplicate</span> </li> </ul> <p> I don't believe this issue is a dupe of <a class="reopened ticket" href="https://svn.boost.org/trac10/ticket/7028" title="#7028: Feature Requests: NDEBUG should disable asserts even if BOOST_ENABLE_ASSERT_HANDLER is ... (reopened)">#7028</a>. That issue (which I disagree with) suggests that all the assert macros be processed out when <code>NDEBUG</code> is defined, even when <code>BOOST_ENABLE_ASSERT_HANDLER</code> is defined. This issue is specifically about making <code>BOOST_ASSERT_MSG</code> consistent with the other macros, which are currently left in always when <code>BOOST_ENABLE_ASSERT_HANDLER</code> is defined. </p> Ticket viboes Thu, 14 Mar 2013 21:29:51 GMT <link>https://svn.boost.org/trac10/ticket/8278#comment:4 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/8278#comment:4</guid> <description> <p> <a class="reopened ticket" href="https://svn.boost.org/trac10/ticket/7028" title="#7028: Feature Requests: NDEBUG should disable asserts even if BOOST_ENABLE_ASSERT_HANDLER is ... (reopened)">#7028</a> patch makes the 3 macros uniform. Could you provide a patch that clarifies what do you expect? </p> </description> <category>Ticket</category> </item> <item> <dc:creator>viboes</dc:creator> <pubDate>Thu, 14 Mar 2013 21:56:25 GMT</pubDate> <title/> <link>https://svn.boost.org/trac10/ticket/8278#comment:5 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/8278#comment:5</guid> <description> <p> Replying to <a class="ticket" href="https://svn.boost.org/trac10/ticket/8278#comment:4" title="Comment 4">viboes</a>: </p> <blockquote class="citation"> <p> <a class="reopened ticket" href="https://svn.boost.org/trac10/ticket/7028" title="#7028: Feature Requests: NDEBUG should disable asserts even if BOOST_ENABLE_ASSERT_HANDLER is ... (reopened)">#7028</a> patch makes the 3 macros uniform. Could you provide a patch that clarifies what do you expect? </p> </blockquote> <p> Oh, I think I understand the issue now. See <a class="reopened ticket" href="https://svn.boost.org/trac10/ticket/7028" title="#7028: Feature Requests: NDEBUG should disable asserts even if BOOST_ENABLE_ASSERT_HANDLER is ... (reopened)">#7028</a>. </p> </description> <category>Ticket</category> </item> <item> <dc:creator>Eric Niebler</dc:creator> <pubDate>Thu, 14 Mar 2013 22:00:03 GMT</pubDate> <title>attachment set https://svn.boost.org/trac10/ticket/8278 https://svn.boost.org/trac10/ticket/8278 <ul> <li><strong>attachment</strong> → <span class="trac-field-new">assert.patch</span> </li> </ul> Ticket Eric Niebler Thu, 14 Mar 2013 22:01:10 GMT <link>https://svn.boost.org/trac10/ticket/8278#comment:6 </link> <guid isPermaLink="false">https://svn.boost.org/trac10/ticket/8278#comment:6</guid> <description> <p> I've attached a patch that addressed the problem the way I think it should be addressed, and the way that is least surprising for existing users of <code>BOOST_ASSERT</code>. It should be applied to trunk as it is as of <a class="changeset" href="https://svn.boost.org/trac10/changeset/83430" title="Added missing header for is_nothrow_move_constructible (refs #8189).">[83430]</a>. </p> </description> <category>Ticket</category> </item> </channel> </rss>