[Quantlib-dev] [ quantlib-Patches-3542397 ] Define boost::assertion_failed_msg due to changes on boost

[SourceForge.net <no...@so...>]

Patches item #3542397, was opened at 2012-07-10 19:46
Message generated for change (Comment added) made by lballabio
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=312740&aid=3542397&group_id=12740

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
>Status: Closed
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Piter Dias (piterdias)
>Assigned to: Luigi Ballabio (lballabio)
Summary: Define boost::assertion_failed_msg due to changes on boost

Initial Comment:
boost/array.hpp is now using BOOST_ASSERT_MSG instead of BOOST_ASSERT.
When BOOST_ENABLE_ASSERT_HANDLER is defined, like in qldefines.hpp, BOOST_ASSERT_MSG requires user defined function boost::assertion_failed_msg, but boost/array.hpp doesn't define it.
QuantLibXL fails due use of boost/array.hpp on sabrvolsurface.hpp.

----------------------------------------------------------------------

Comment By: Luigi Ballabio (lballabio)
Date: 2012-07-12 03:30

Message:
The patch was applied to the code repository.
It will be included in next release.
Thank you.


----------------------------------------------------------------------

Comment By: Piter Dias (piterdias)
Date: 2012-07-11 18:57

Message:
Moved to  ql/errors.cpp and changed to work like boost::assertion_failed
(plus msg output).

----------------------------------------------------------------------

Comment By: Luigi Ballabio (lballabio)
Date: 2012-07-11 02:14

Message:
Ok, but:
1) I would add the function to ql/errors.cpp where boost::assertion_failed
is also defined (no need to include it in each file through qlconfig.hpp);
2) I would have it throw an exception like assertion_failed does, instead
of aborting.


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=312740&aid=3542397&group_id=12740