2003-04-08 Jonathan Wakely <redi@gcc.gnu.org>

	* doc/extend.texi (Template Instantiation): Refer to ISO standard,
	not Working Paper.
	* doc/invoke.texi (C++ Dialect Options): Same.


git-svn-id: svn+ssh://gcc.gnu.org/svn/gcc/trunk@65456 138bc75d-0d04-0410-961f-82ee72b054a4

gcc/ChangeLog

@@ -1,3 +1,9 @@
+2003-04-08  Jonathan Wakely  <redi@gcc.gnu.org>
+
+	* doc/extend.texi (Template Instantiation): Refer to ISO standard,
+	not Working Paper.
+	* doc/invoke.texi (C++ Dialect Options): Same.
+
 2003-04-10  Zack Weinberg  <zack@codesourcery.com>
 
 	* tree.c (tree_operand_check_failed): New function.

gcc/doc/extend.texi

@@ -7428,8 +7428,8 @@ compile it without @option{-fno-implicit-templates} so you get all of the
 instances required by your explicit instantiations (but not by any
 other files) without having to specify them as well.
 
-g++ has extended the template instantiation syntax outlined in the
-Working Paper to allow forward declaration of explicit instantiations
+g++ has extended the template instantiation syntax given in the ISO
+standard to allow forward declaration of explicit instantiations
 (with @code{extern}), instantiation of the compiler support data for a
 template class (i.e.@: the vtable) without instantiating any of its
 members (with @code{inline}), and instantiation of only the static data

gcc/doc/invoke.texi

@@ -1281,14 +1281,14 @@ around bugs in the access control code.
 @item -fcheck-new
 @opindex fcheck-new
 Check that the pointer returned by @code{operator new} is non-null
-before attempting to modify the storage allocated.  The current Working
-Paper requires that @code{operator new} never return a null pointer, so
-this check is normally unnecessary.
-
-An alternative to using this option is to specify that your
-@code{operator new} does not throw any exceptions; if you declare it
-@samp{throw()}, G++ will check the return value.  See also @samp{new
-(nothrow)}.
+before attempting to modify the storage allocated.  This check is
+normally unnecessary because the C++ standard specifies that
+@code{operator new} will only return @code{0} if it is declared
+@samp{throw()}, in which case the compiler will always check the
+return value even without this option.  In all other cases, when
+@code{operator new} has a non-empty exception specification, memory
+exhaustion is signalled by throwing @code{std::bad_alloc}.  See also
+@samp{new (nothrow)}.
 
 @item -fconserve-space
 @opindex fconserve-space