feedc0de/boost_preprocessor
1
0
Fork 0
forked from boostorg/preprocessor
Code Pull Requests Activity

Updated docs __VA_OPT__ support.

Browse Source
This commit is contained in:
Edward Diener
2019-10-30 14:32:45 -04:00
parent 4fe7807f79
commit a9827c8fc8
2 changed files with 4 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
doc/headers/facilities.html
View File

@ -15,6 +15,7 @@
<ul>
<li><a href="facilities/apply.html">&lt;boost/preprocessor/facilities/apply.hpp&gt;</a></li>
<li><a href="facilities/empty.html">&lt;boost/preprocessor/facilities/empty.hpp&gt;</a></li>
<li><a href="facilities/check_empty.html">&lt;boost/preprocessor/facilities/check_empty.hpp&gt;</a></li>
<li><a href="facilities/expand.html">&lt;boost/preprocessor/facilities/expand.hpp&gt;</a></li>
<li><a href="facilities/identity.html">&lt;boost/preprocessor/facilities/identity.hpp&gt;</a></li>
<li><a href="facilities/intercept.html">&lt;boost/preprocessor/facilities/intercept.hpp&gt;</a></li>

6
doc/topics/emptiness.html
View File

@ -32,11 +32,11 @@
<h4>Expanding to nothing</h4>
<div>
Given certain arguments a macro might expand to nothing, aka no preprocessor tokens. This may
happen more than the previous case of an argument to a macro being nothing because the expansion of a macro
happen more than in the previous case of an argument to a macro being nothing because the expansion of a macro
is often used to initialize some C++ construct, and C++ has some places where
a part of a compile-time construct can be empty. However a macro which expands to nothing
rarely occurs when a macro's expansion is used as an argument to another macro, although
again it is perfectly legal C++.
rarely occurs when that macro's expansion is used as an argument to another macro because we would again have
a macro where we are passing nothing as an argument.
</div>
<div class="code">
<pre>