db/pgbackrest
1
0
Fork 0
mirror of https://github.com/pgbackrest/pgbackrest.git synced 2025-05-13 21:56:42 +02:00
Code Issues Releases Activity

Add CHECK() macro for production assertions.

Browse Source 
CHECK() works just like ASSERT() but is kept in production builds.
This commit is contained in:
David Steele 2019-04-18 13:21:24 -04:00
parent b258aec0ad
commit 670fa88a98
2 changed files with 14 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/xml/release.xml
View File

@ -29,6 +29,10 @@
<p>Move <code>lockRelease()</code> to the end of <code>exitSafe()</code>.</p> <p>Move <code>lockRelease()</code> to the end of <code>exitSafe()</code>.</p>
</release-item> </release-item>
<release-item>
<p>Add <code>CHECK()</code> macro for production assertions.</p>
</release-item>
<release-item> <release-item>
<p>Automatically generate constants for command and option names.</p> <p>Automatically generate constants for command and option names.</p>
</release-item> </release-item>

10
src/common/assert.h
View File

@ -21,5 +21,15 @@ Asserts are used in test code to ensure that certain conditions are true. They
#define ASSERT(condition) #define ASSERT(condition)
#endif #endif
/***********************************************************************************************************************************
Checks are used in production builds to test very important conditions. Be sure to limit use to the most critical cases.
***********************************************************************************************************************************/
#define CHECK(condition) \
do \
{ \
if (!(condition)) \
THROW_FMT(AssertError, "check '%s' failed", #condition); \
} \
while (0)
#endif #endif