On Mon, Jun 25, 2012 at 4:56 PM, Jeffrey Lee Hellrung, Jr. < jeffrey.hellrung@gmail.com> wrote:
On Mon, Jun 25, 2012 at 4:49 PM, Emil Dotchevski> boost::exception stores the BOOST_THROW_EXCEPTION information in a custom,
more efficient way than other data. The only overhead is the potential bloat from BOOST_CURRENT_FUNCTION, which now can be controlled (see ticket #6450.)
At least in my experience BOOST_THROW_EXCEPTION is very helpful in combination with boost::diagnostic_information. In my development environment, I can double-click the message to go to the location of the throw, which makes it easy to set a break point and run again to see the context in which the unexpected exception happens.
Hmmm...should these details be added to the BOOST_THROW_EXCEPTION documentation? It's not at all clear from the documentation what overhead BOOST_THROW_EXCEPTION brings relative to simply boost::throw_exception.
Yes, good idea. I'll add this info in the documentation. Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode