Great g++ bug! Local destructor isn't called!
Moore, Mathew L
Wed Mar 10 16:02:00 GMT 2004
> BTW, in general, I've found that it's usually best NOT to put
> in throw
> specifications for functions / methods. Ever. (This
> restriction does not
> apply to putting in the "throw() -- I throw nothing, ever"
> specification. But even that should be used with great caution.)
Just out of curiosity, what is the reasoning for this? Is this for g++
specifically, or C++ in general?
> If C++ did exception specifications like how Java does them,
> then that'd be
> a different story.
More information about the Gcc-help