From: Emil Dotchevski (emildotchevski_at_[hidden])
Date: 2006-09-13 17:40:11
> Point one: Get real. People rarely have time to analyze exception safety.
You can make the same point just about any correct programming approach. Why
do it correctly when you can hack your way to something that works?
> Point two:
> All C code is exception-safe by definition. It's much easier
> to audit C code because one doesn't have to think about rather
> unusual path of execution.
In C you still have undefined behavior. More to the point, overflowing a
signed integer is undefined behavior in C. The compiler is free to generate
code which does anything at all in this case, like send a nasty email to
your boss. Or throw a C++ exception.
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk