feedc0de/boost_assert
1
0
Fork 0
forked from boostorg/assert
Code Pull Requests Activity

Line wrap to ~80 columns because PDF

Browse Source
This commit is contained in:
Peter Dimov
2017-06-06 06:02:19 +03:00
parent 30c7c8077a
commit 5f15c119fc
2 changed files with 16 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
doc/assert.adoc
View File

@@ -32,8 +32,8 @@ code.
is included, `BOOST_ASSERT(expr)` expands to
+
```
(BOOST_LIKELY(!!(expr))? ((void)0):
::boost::assertion_failed(#expr, BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))
(BOOST_LIKELY(!!(expr))? ((void)0): ::boost::assertion_failed(#expr,
BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))
```
+
That is, it evaluates `expr` and if it's false, calls
@@ -45,7 +45,8 @@ This is true regardless of whether `NDEBUG` is defined.
```
namespace boost
{
void assertion_failed(char const * expr, char const * function, char const * file, long line);
void assertion_failed(char const * expr, char const * function,
char const * file, long line);
}
```
+
@@ -74,8 +75,8 @@ the macro `NDEBUG` is defined.
is included, `BOOST_ASSERT_MSG(expr,msg)` expands to
+
```
(BOOST_LIKELY(!!(expr))? ((void)0):
::boost::assertion_failed_msg(#expr, msg, BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))
(BOOST_LIKELY(!!(expr))? ((void)0): ::boost::assertion_failed_msg(#expr,
msg, BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))
```
+
This is true regardless of whether `NDEBUG` is defined.
@@ -85,8 +86,8 @@ This is true regardless of whether `NDEBUG` is defined.
```
namespace boost
{
void assertion_failed_msg(char const * expr, char const * msg, char const * function,
char const * file, long line);
void assertion_failed_msg(char const * expr, char const * msg,
char const * function, char const * file, long line);
}
```
+

15
doc/html/assert.html
View File

@@ -482,8 +482,8 @@ affecting the definition of the standard <code>assert</code>.</p>
is included, <code>BOOST_ASSERT(expr)</code> expands to</p>
<div class="listingblock">
<div class="content">
<pre class="highlight"><code>(BOOST_LIKELY(!!(expr))? ((void)0):
::boost::assertion_failed(#expr, BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))</code></pre>
<pre class="highlight"><code>(BOOST_LIKELY(!!(expr))? ((void)0): ::boost::assertion_failed(#expr,
BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))</code></pre>
</div>
</div>
<div class="paragraph">
@@ -498,7 +498,8 @@ This is true regardless of whether <code>NDEBUG</code> is defined.</p>
<div class="content">
<pre class="highlight"><code>namespace boost
{
void assertion_failed(char const * expr, char const * function, char const * file, long line);
void assertion_failed(char const * expr, char const * function,
char const * file, long line);
}</code></pre>
</div>
</div>
@@ -540,8 +541,8 @@ the macro <code>NDEBUG</code> is defined.</p>
is included, <code>BOOST_ASSERT_MSG(expr,msg)</code> expands to</p>
<div class="listingblock">
<div class="content">
<pre class="highlight"><code>(BOOST_LIKELY(!!(expr))? ((void)0):
::boost::assertion_failed_msg(#expr, msg, BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))</code></pre>
<pre class="highlight"><code>(BOOST_LIKELY(!!(expr))? ((void)0): ::boost::assertion_failed_msg(#expr,
msg, BOOST_CURRENT_FUNCTION, __FILE__, __LINE__))</code></pre>
</div>
</div>
<div class="paragraph">
@@ -554,8 +555,8 @@ is included, <code>BOOST_ASSERT_MSG(expr,msg)</code> expands to</p>
<div class="content">
<pre class="highlight"><code>namespace boost
{
void assertion_failed_msg(char const * expr, char const * msg, char const * function,
char const * file, long line);
void assertion_failed_msg(char const * expr, char const * msg,
char const * function, char const * file, long line);
}</code></pre>
</div>
</div>