$include_dir="/home/hyper-archives/boost-commit/include"; include("$include_dir/msg-header.inc") ?>
From: asutton_at_[hidden]
Date: 2007-07-24 21:15:17
Author: asutton
Date: 2007-07-24 21:15:17 EDT (Tue, 24 Jul 2007)
New Revision: 7533
URL: http://svn.boost.org/trac/boost/changeset/7533
Log:
Cleaning up some comments
Text files modified: 
   sandbox/boost_docs/trunk/libs/standard/doc/concepts/utilities/default_constructible.qbk |    11 -----------                             
   1 files changed, 0 insertions(+), 11 deletions(-)
Modified: sandbox/boost_docs/trunk/libs/standard/doc/concepts/utilities/default_constructible.qbk
==============================================================================
--- sandbox/boost_docs/trunk/libs/standard/doc/concepts/utilities/default_constructible.qbk	(original)
+++ sandbox/boost_docs/trunk/libs/standard/doc/concepts/utilities/default_constructible.qbk	2007-07-24 21:15:17 EDT (Tue, 24 Jul 2007)
@@ -51,20 +51,9 @@
 ]
 
 [heading Notes]
-In addition to requiring default cosntructability, there is an implicit requirement
-on destructability. A locally declared automatic variable of [StdDefaultConstructible]
-type `T` will eventually go out of scope, requiring `T`'s destructor to be called. If the
-destructor is not public, then this `T` cannot model the [StdDefaultConstructible] concept.
-
 If the default constructor of a class type `T` is `private`, then the `T` does not
 model the [StdDefaultConstructible] concept.
 
-[note
-*TODO:* There could be some discussion about default constructabiltiy and arrays,
-and its use in the `new` expressions. Maybe we should make `Constructible` and
-`Destructible` real concepts (with this level of documentation).
-]
-
 [heading Examples]
 All fundamental types in C++ are [StdDefaultConstructible] but may not have default
 values, depending on how they are constructed.