Difference between revisions of "Cpp Coding Standards/ERR"
From Apache OpenOffice Wiki
m (→Function Safety Guarantees <span id="Safe">(Safe)</span>) |
m (Cpp Coding Standards/Error Handling moved to Cpp Coding Standards/ERR: consistency) |
(No difference)
|
Revision as of 15:54, 22 May 2007
Topic-Id: ERR
How to distinguish and use exceptions, assertions and other error cases.
Contents
Summary
Assert Assumptions (Assert)
Assert liberally to document internal assumptions and invariants. Don't use assertions for runtime errors. Ensure that assertions don't perform side effects.
Function Safety Guarantees (Safe)
Provide the strongest error-safety guarantee for each function that does not punish callers who do not need it. The basic guarantee is always necessary.
Which Functions Never Fail (NoFail)
Destructors, delete operators and swap functions must never fail. Occurring exceptions have to be catched and handled within the same function.
Throwing and Catching Exceptions (HowThrow)
Throw exceptions by value, catch them by reference.
Avoid Exception Specifications (ExSpec)
Don't write exception specifications on your functions.
Related Rules
- PRINC:ErrHdl - Consistent Error Handling