Boost logo

Boost :

From: David Abrahams (dave_at_[hidden])
Date: 2002-09-17 11:09:38

From: "Peter Dimov" <pdimov_at_[hidden]>

> Also, smart_ptr.htm says that
> "The only exception ever thrown by functions which do throw (assuming T
> meets the common requirements) is std::bad_alloc, and that is thrown only
> functions which are explicitly documented as possibly throwing
> std::bad_alloc."
> but this is too strict. For instance, in some implementations the
> constructor can fail if it cannot create the mutex that protects the
> reference count.
> Comments? Rationale for the original text?

All I can say was that it was true with the original non-threadsafe
shared_ptr design.


           David Abrahams * Boost Consulting
dave_at_[hidden] *

Boost list run by bdawes at, gregod at, cpdaniel at, john at