From c5846378ab2789f82510bbc80ac5a1a8dacddb6e Mon Sep 17 00:00:00 2001 From: Beman Dawes Date: Fri, 13 Jul 2001 16:32:34 +0000 Subject: [PATCH] More FAQ entries added. [SVN r10605] --- shared_ptr.htm | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/shared_ptr.htm b/shared_ptr.htm index 3f6c7df..c9fe1e6 100644 --- a/shared_ptr.htm +++ b/shared_ptr.htm @@ -247,6 +247,14 @@ supply an automatic conversion to T*?
A. As an aid to writing test cases and debugging displays. One of the progenitors had use_count(), and it was useful in tracking down bugs in a complex project that turned out to have cyclic-dependencies.

+

Q. Why doesn't shared_ptr specify complexity requirements?
+A. Because complexity limit implementors and complicate the specification without apparent benefit to +shared_ptr users. For example, error-checking implementations might become non-conforming if they +had to meet stringent complexity requirements.

+

Q. Why doesn't shared_ptr provide (your pet feature here)?
+A. Because (your pet feature here) would mandate a reference counted (or a link-list, or ...) implementation. This is not the intent. +[Provided by Peter Dimov]
+


Revised 13 July, 2001