Darren New wrote:
which is bad, bad, bad, but normally you'd be using a boost::scoped_ptr
I.e., there are so *many* ways to screw up, you have to pick exactly
the right one to get the compiler to tell you.
Personally, it boggles my mind when I see G++ issue warnings for
things that can't possibly work right. Shouldn't "your program will
act in undefined ways if you invoke this function" be an error?
Most languages/compilers fail to identify all the possible scenarios
that can end in disaster. Truth be told, good C++ compilers these days
do a remarkable job of catching "undefined behavior".
--Chris
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
