Hi,
It has exactly the same behavior as BOOST_ASSERT, except that the expression that is passed to BOOST_VERIFY is always evaluated.
Does it just evaluate the expression or does it also fail is it evaluates to false? Why is there no BOOST_VERIFY_MSG? http://www.boost.org/doc/libs/1_46_1/libs/utility/assert.html#BOOST_VERIFY Greetings, -- Olaf
Olaf van der Spek wrote:
It has exactly the same behavior as BOOST_ASSERT, except that the expression that is passed to BOOST_VERIFY is always evaluated.
Does it just evaluate the expression or does it also fail is it evaluates to false?
It fails, just as BOOST_ASSERT does. The only difference is that the expression is evaluated.
Why is there no BOOST_VERIFY_MSG?
There wasn't any demand, I guess. I can rationalize its absence as follows: if the side effects of the expression are significant, one probably doesn't feel a need to add a message, as the expression itself is descriptive enough.
Olaf van der Spek wrote:
It has exactly the same behavior as BOOST_ASSERT, except that the expression that is passed to BOOST_VERIFY is always evaluated.
Does it just evaluate the expression or does it also fail is it evaluates to false?
BOOST_VERIFY is just like BOOST_ASSERT in non-NDEBUG builds. The difference is in NDEBUG builds when BOOST_ASSERT is a NOP and BOOST_VERIFY still evaluates its expression.
Why is there no BOOST_VERIFY_MSG?
Beman recently added BOOST_VERIFY_MSG and, perhaps, didn't use BOOST_VERIFY and so didn't think to add BOOST_VERIFY_MSG. If you think it is a valuable addition, you can write it up in Trac and, even better, submit a patch with the code and documentation. _____ Rob Stewart robert.stewart@sig.com Software Engineer using std::disclaimer; Dev Tools & Components Susquehanna International Group, LLP http://www.sig.com IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses.
On Mon, Apr 11, 2011 at 1:10 PM, Stewart, Robert <Robert.Stewart@sig.com> wrote:
Olaf van der Spek wrote:
It has exactly the same behavior as BOOST_ASSERT, except that the expression that is passed to BOOST_VERIFY is always evaluated.
Does it just evaluate the expression or does it also fail is it evaluates to false?
BOOST_VERIFY is just like BOOST_ASSERT in non-NDEBUG builds. The difference is in NDEBUG builds when BOOST_ASSERT is a NOP and BOOST_VERIFY still evaluates its expression.
That part is clear, but what does it do when the expression evaluates to false? That's not clear from the docs.
Why is there no BOOST_VERIFY_MSG?
Beman recently added BOOST_VERIFY_MSG and, perhaps, didn't use
You mean BOOST_ASSERT_MSG?
BOOST_VERIFY and so didn't think to add BOOST_VERIFY_MSG. If you think it is a valuable addition, you can write it up in Trac and, even better, submit a patch with the code and documentation.
_____ Rob Stewart robert.stewart@sig.com Software Engineer using std::disclaimer; Dev Tools & Components Susquehanna International Group, LLP http://www.sig.com
IMPORTANT: The information contained in this email and/or its attachments is confidential. If you are not the intended recipient, please notify the sender immediately by reply and immediately delete this message and all its attachments. Any review, use, reproduction, disclosure or dissemination of this message or any attachment by an unintended recipient is strictly prohibited. Neither this message nor any attachment is intended as or should be construed as an offer, solicitation or recommendation to buy or sell any security or other financial instrument. Neither the sender, his or her employer nor any of their respective affiliates makes any warranties as to the completeness or accuracy of any of the information contained herein or that this message or any of its attachments is free of viruses. _______________________________________________ Unsubscribe & other changes: http://lists.boost.org/mailman/listinfo.cgi/boost
-- Olaf
participants (3)
-
Olaf van der Spek -
Peter Dimov -
Stewart, Robert