* Vassilii Khachaturov -- Friday 25 November 2005 15:11: > * whenever an exception object was created on a stack and then thrown > (thus causing the dtor for that object to fire!), it was replaced > with a STATIC exception
The whole thing looks like a solution desperately searching for a problem. The reasoning for this patch contradicts Stroustrup, who has several examples of what we are doing in "The C++ programming language". Maybe it's only because I'm using an older copy (2nd ed.), but he writes (p. 602, "r.15.2 Throwing an Exception"): "A throw-expression initializes a temporary object of the static type of the operand of throw and uses that temporary to initialize the appropriately-typed variable named in the handler." The throw expression cares for the thrown class to be available until it reached the handler. No need to spread ugly static variables everywhere. Our code looks right for me as it is. But then again, I'm a relative C++ newbie ... :-) m. _______________________________________________ Flightgear-devel mailing list [email protected] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
