diff options
| author | Torstein Husebø <torstein@huseboe.net> | 2016-02-08 13:27:22 +0100 |
|---|---|---|
| committer | Torstein Husebø <torstein@huseboe.net> | 2016-02-24 11:56:11 +0100 |
| commit | 96d490114900686b4d17f9b751fab6e39cfcc560 (patch) | |
| tree | 150de8b7f09fd85572ade2ddbc53d1769e36bcf9 /CODING_STYLE | |
| parent | 77d9510adc57224946393ed4fdc4e0468e3b501d (diff) | |
treewide: fix typos and then/that use
Diffstat (limited to 'CODING_STYLE')
| -rw-r--r-- | CODING_STYLE | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CODING_STYLE b/CODING_STYLE index 46e366898e..e5ba396368 100644 --- a/CODING_STYLE +++ b/CODING_STYLE @@ -163,7 +163,7 @@ programming error with assert_return() and return a sensible return code. In all other calls, it is recommended to check for programming errors with a more brutal assert(). We are more forgiving to public - users then for ourselves! Note that assert() and assert_return() + users than for ourselves! Note that assert() and assert_return() really only should be used for detecting programming errors, not for runtime errors. assert() and assert_return() by usage of _likely_() inform the compiler that he should not expect these checks to fail, |