From 92999be43626c9271226777a7408fbe11b9894ce Mon Sep 17 00:00:00 2001
From: Peter Dimov
The support for custom deallocators does not impose significant overhead. Other shared_ptr features still require a deallocator to be kept.
-The requirement that the copy constructor of D does not throw is too strong. - It will be removed when some core language issues are resolved (cv-qualified - function types, partial ordering clarifications.)]
+The requirement that the copy constructor of D does not throw is too + strong. It will be removed when some core language issues are resolved + (cv-qualified function types, partial ordering clarifications.)]
shared_ptr(shared_ptr const & r); // never throws template<typename Y> shared_ptr(shared_ptr<Y> const & r); // never throws
@@ -286,8 +286,7 @@ template<typename Y> shared_ptr(shared_ptr<Y> const & r); // nevtemplate<typename Y> shared_ptr(std::auto_ptr<Y> & r);Effects: Constructs a shared_ptr, as if by storing a copy of r.release().
-Postconditions: use count for all copies is - increased by one.
+Postconditions: use count is 1.
Throws: std::bad_alloc.
Exception safety: If an exception is thrown, the constructor has no effect.