Update references to C++ working paper

Jason Merrill jason@redhat.com
Thu Apr 10 08:29:00 GMT 2003


On Tue, 8 Apr 2003 16:17:38 +0100, Jonathan Wakely <cow@compsoc.man.ac.uk> wrote:

>  @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
> +before attempting to modify the storage allocated.  The ISO standard
> +requires that @code{operator new} never return a null pointer, so
>  this check is normally unnecessary.

Actually, the standard makes an exception for operator new functions which
are declared throw(), so the compiler checks the return value on such
functions even without -fcheck-new.  Would you mind adding a note about
that?

Jason



More information about the Gcc-patches mailing list