From: Peter Dimov (pdimov_at_[hidden])
Date: 2002-09-17 08:19:22


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 by
functions which are explicitly documented as possibly throwing
std::bad_alloc."

but this is too strict. For instance, in some implementations the shared_ptr
constructor can fail if it cannot create the mutex that protects the
reference count.

Comments? Rationale for the original text?