g++: new that throw bad_alloc ?

[Mark Mitchell]

>>>>> "Mike" == Mike Stump <mrs@wrs.com> writes:

    Mike> Do others think we should just turn on a throwing new, and
    Mike> work it that way?

I, for one, think g++ should do this.  It's going to break existing
code, I know, and it may not work at first.  But, the developers are
working hard on g++ at the moment, and on exception-handling in
particular.  Furthermore, we seem to be breaking a lot of existing
code at the moment.  At the source level, g++ just recently picked up
the new template rules for specializations, and stopped accepting
guiding declarations.  At the object level, we changed the
name-mangling scheme, and, I believe, vtable layout.  Let's
make all the breaks at once; that way users will only have to port 
their code from the old version to the new version once.  The compiler
has also been moving closer and closer to the CD2; this change would
be (another) important step in that direction.

-- 
Mark Mitchell		mmitchell@usa.net
Stanford University	http://www.stanford.edu