egcs bug? arrgh

[Martin v. Loewis]

> When it is added, the double-destruction disappears and all seems
> well again.  I still say "semi-false alarm" as it may be good to
> have this warning show up even when -Wall is not used as "bad" code
> is generated silently otherwise

It is, in general, not possible to determine (statically) whether a
function returns a value or not. Therefore, your code has "undefined"
behaviour. It is still correct C++; the compiler shouldn't warn -
there might be "legal" uses of similar constructs, in which case a
warning would be annoying.

Regards,
Martin