Re: Exception Misconceptions: Exceptions are for unrecoverable
errors.
In article <4d3ba575-becf-4c40-be44-7e4d12fff3a8@p8g2000yqb.googlegroups.com>, James Kanze <james.kanze@gmail.com> wrote:
On Dec 22, 9:34 pm, ta...@mongo.net (tanix) wrote:
In article
<exceptions-20091222164...@ram.dialup.fu-berlin.de>,
r...@zedat.fu-berlin.de (Stefan Ram) wrote:
[...]
More elegantly? Actually, for correct and secure C++ code,
all functions need to be written to be =BBexception safe=AB,
Correct.
Almost everything you do will generate some kind of exception,
at least in modern languages, and it is good it does.
In order to write exception safe code, at least with value
semantics (and I suspect even without value semantics, but I've
not analysed the question in detail), it's been proven that you
need a certain number of primitives which are guaranteed not to
throw---one of the most classical C++ idioms, for example, only
works if you have a version of swap that doesn't throw.
Cool. I like that. You ARE pretty inventive I'd say.
:--}
--
Programmer's Goldmine collections:
http://preciseinfo.org
Tens of thousands of code examples and expert discussions on
C++, MFC, VC, ATL, STL, templates, Java, Python, Javascript,
organized by major topics of language, tools, methods, techniques.