On Thu, Mar 24, 2011 at 4:50 PM, Dave Abrahams <dave@boostpro.com> wrote:
At Thu, 24 Mar 2011 11:27:23 -0700, Emil Dotchevski wrote:
That said, "libraries should generally use BOOST_THROW_EXCEPTION" is a good rule for Boost, and I wouldn't mind having something like it in the inspect tests, provided that libraries with a legitimate reason not to use it can be registered as exceptions to the rule.
Maybe I'm missing something but what is an example of such a legitimate reason?
For example, "it buys nothing, because the library can't really work as coded without exception support." Such is the case for Boost.Python, I believe.
Whether it makes the library useful in BOOST_NO_EXCEPTIONS builds is best left for the user of the library to decide. At any rate, you gain nothing from not using BOOST_THROW_EXCEPTION. Besides, even if the library remains useless in BOOST_NO_EXCEPTIONS builds, I wouldn't say that BOOST_THROW_EXCEPTION buys nothing. Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode