g++: new that throw bad_alloc ?

Joe Buck jbuck@synopsys.com
Fri Oct 10 22:46:00 GMT 1997


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

It's really risk-free to do the right thing.  The reason is that
the current default behavior is to just kill the whole program if
new fails (after any new-handlers get a chance).  Even if the throwing
new dumps core instead, that is no worse than what users have now.





More information about the Gcc mailing list