Difference between revisions of "Cpp Coding Standards/ERR"
From Apache OpenOffice Wiki
m |
m |
||
| (6 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
| − | == | + | == Error Handling (ERR) == |
| − | How to distinguish and | + | ''How to distinguish and use exceptions, assertions and other error cases.'' |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
| − | ==== | + | ===== Assert Assumptions <span id="Assert">(Assert)</span> ===== |
| − | + | Assert liberally to document internal assumptions and invariants. Don't use assertions for runtime errors.<br> | |
| + | Ensure that assertions don't perform side effects.<br> | ||
| + | [[/Assert|-> Details]] | ||
| − | ==== | + | ===== Function Safety Guarantees <span id="Safe">(Safe)</span> ===== |
| − | + | 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. [[/Safe|-> Details]] | |
| − | ==== | + | ===== Which Functions Never Fail <span id="NoFail">(NoFail)</span> ===== |
| − | + | Destructors, delete operators and swap functions must never fail. Occurring exceptions have to be catched and handled within the same function. [[/NoFail|-> Details]] | |
| − | ==== | + | ===== Throwing and Catching Exceptions <span id="HowThrow">(HowThrow)</span> ===== |
| − | + | Throw exceptions by value, catch them by reference. [[/HowThrow|-> Details]] | |
| − | Exception | + | ===== Avoid Exception Specifications <span id="ExSpec">(ExSpec)</span> ===== |
| − | + | Don't write exception specifications on your functions. [[/ExSpec|-> Details]] | |
| − | + | ||
| − | + | ||
| − | + | ||
| − | + | ||
---- | ---- | ||
[[Category:Coding Standards]] | [[Category:Coding Standards]] | ||
Latest revision as of 09:05, 23 May 2007
Contents
Error Handling (ERR)
How to distinguish and use exceptions, assertions and other error cases.
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.
-> Details
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. -> Details
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. -> Details
Throwing and Catching Exceptions (HowThrow)
Throw exceptions by value, catch them by reference. -> Details
Avoid Exception Specifications (ExSpec)
Don't write exception specifications on your functions. -> Details
