Re: [boost] [utility] [assert] Proposal for a new assert macro which stores the failed values ("informative assert")

I second the problem with BOOST_ASSERT_MSG. And I'm thinking it can be

trivially worked around: BOOST_ASSERT_MSG could be (conditionally) defined like so:

#if defined(BOOST_ASSERT_MSG_SIMPLIFIED) #define BOOST_ASSERT_MSG( expr, msg ) assert( (expr) || !msg ) #else ... #endif

I might get something wrong, but why not simply #define BOOST_ASSERT_MSG( expr, msg ) assert( expr)? The point of the msg-part, to me, is to serialize variables?