Boost 1.47 and exception_ptr

Travis Gockel

28 Oct 2011 28 Oct '11

6:02 p.m.

I'm working on upgrading from Boost 1.46.1 to 1.47 and having one tiny little problem with exception_ptr. Currently, some of my systems keep an exception_ptr around to denote if they have a "current exception" or not. At times, we need to "clear" the current exception (it was resolved or whatever), which we used to do by calling ex->reset(). However, as of 1.47, excecption_ptr is no longer just a shared_ptr, so reset() has gone away. What is the new preferred way of getting this old functionality? I can't seem to find the way in the source. -- Travis Gockel C++ Pirate

Attachments:

attachment.html (text/html — 660 bytes)

Show replies by date

Emil Dotchevski

29 Oct 29 Oct

12:18 a.m.

On Fri, Oct 28, 2011 at 11:02 AM, Travis Gockel wrote:

...

I'm working on upgrading from Boost 1.46.1 to 1.47 and having one tiny little problem with exception_ptr. Currently, some of my systems keep an exception_ptr around to denote if they have a "current exception" or not. At times, we need to "clear" the current exception (it was resolved or whatever), which we used to do by calling ex->reset(). However, as of 1.47, excecption_ptr is no longer just a shared_ptr, so reset() has gone away. What is the new preferred way of getting this old functionality? I can't seem to find the way in the source.

The official documentation for boost::exception_ptr is at www.boost.org/doc/libs/release/libs/exception/doc/exception_ptr.html. Essentially, boost::exception_ptr is default-constructable, so you can do ex=boost::exception_ptr(). Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode

Travis Gockel

3:59 a.m.

D'oh! It seems like the simplest of things are the most difficult to find. Thanks ;-) On Fri, Oct 28, 2011 at 6:18 PM, Emil Dotchevski wrote:

...

On Fri, Oct 28, 2011 at 11:02 AM, Travis Gockel wrote:

...
I'm working on upgrading from Boost 1.46.1 to 1.47 and having one tiny little problem with exception_ptr. Currently, some of my systems keep an exception_ptr around to denote if they have a "current exception" or not. At times, we need to "clear" the current exception (it was resolved or whatever), which we used to do by calling ex->reset(). However, as of 1.47, excecption_ptr is no longer just a shared_ptr, so reset() has gone away. What is the new preferred way of getting this old functionality? I can't seem to find the way in the source.

The official documentation for boost::exception_ptr is at www.boost.org/doc/libs/release/libs/exception/doc/exception_ptr.html. Essentially, boost::exception_ptr is default-constructable, so you can do ex=boost::exception_ptr().

Emil Dotchevski Reverge Studios, Inc. http://www.revergestudios.com/reblog/index.php?n=ReCode _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org http://lists.boost.org/mailman/listinfo.cgi/boost-users

-- Travis Gockel Boost Ninja, SolidFire

4865

Age (days ago)

4866

Last active (days ago)

List overview

Download

2 comments

2 participants

participants (2)

Emil Dotchevski
Travis Gockel