feedc0de/boost_config
1
0
Fork 0
forked from boostorg/config
Code Pull Requests Activity

Regenerate docs.

Browse Source 
[CI SKIP]
This commit is contained in:
jzmaddock
2020-03-23 21:07:52 +00:00
parent cc915f1055
commit d11a6ebe09
3 changed files with 49 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

47
doc/html/boost_config/boost_macro_reference.html
View File

@ -3250,6 +3250,20 @@
</td>
</tr>
<tr>
<td>
<p>
<code class="computeroutput"><span class="identifier">BOOST_NO_CXX11_UNRESTRICTED_UNION</span></code>
</p>
</td>
<td>
<p>
The compiler does not support an unrestricted union. This is a
union that may contain static data as well as user-defined member
data with non-trivial special member functions.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="computeroutput"><span class="identifier">BOOST_NO_CXX11_USER_DEFINED_LITERALS</span></code>
@ -3977,7 +3991,8 @@
</p>
</th>
</tr></thead>
<tbody><tr>
<tbody>
<tr>
<td>
<p>
<code class="computeroutput"><span class="identifier">BOOST_INLINE_VARIABLE</span></code>
@ -3991,7 +4006,35 @@
for further adjustments to the code.
</p>
</td>
</tr></tbody>
</tr>
<tr>
<td>
<p>
<code class="computeroutput"><span class="identifier">BOOST_IF_CONSTEXPR</span></code>
</p>
</td>
<td>
<p>
Expands to <code class="computeroutput"><span class="keyword">if</span> <span class="keyword">constexpr</span></code>
when supported, or <code class="computeroutput"><span class="keyword">if</span></code>
otherwise.
</p>
</td>
</tr>
<tr>
<td>
<p>
<code class="computeroutput"><span class="identifier">BOOST_INLINE_CONSTEXPR</span></code>
</p>
</td>
<td>
<p>
This is a shortcut for <code class="computeroutput"><span class="identifier">BOOST_INLINE_VARIABLE</span>
<span class="identifier">BOOST_CONSTEXPR_OR_CONST</span></code>.
</p>
</td>
</tr>
</tbody>
</table></div>
</div>
<div class="section">

6
doc/html/boost_config/guidelines_for_boost_authors.html
View File

@ -297,9 +297,9 @@
and name the test file "<code class="computeroutput"><span class="identifier">boost_has_foo</span><span class="special">.</span><span class="identifier">ipp</span></code>".
Try not to add feature test macros unnecessarily, if there is a platform
specific macro that can already be used (for example <code class="computeroutput"><span class="identifier">_WIN32</span></code>,
<code class="computeroutput"><span class="identifier">__BEOS__</span></code>, or <code class="computeroutput"><span class="identifier">__linux</span></code>) to identify the feature then use
that. Try to keep the macro to a feature group, or header name, rather than
one specific API (for example <code class="computeroutput"><span class="identifier">BOOST_HAS_NL_TYPES_H</span></code>
<code class="computeroutput"><span class="identifier">__BEOS__</span></code>, or <code class="computeroutput"><span class="identifier">__linux__</span></code>) to identify the feature then
use that. Try to keep the macro to a feature group, or header name, rather
than one specific API (for example <code class="computeroutput"><span class="identifier">BOOST_HAS_NL_TYPES_H</span></code>
rather than <code class="computeroutput"><span class="identifier">BOOST_HAS_CATOPEN</span></code>).
If the macro describes a POSIX feature group, then add boilerplate code to
<a href="../../../../../boost/config/detail/suffix.hpp" target="_top">&lt;boost/config/detail/suffix.hpp&gt;</a>

2
doc/html/index.html
View File

@ -990,7 +990,7 @@
</div>
</div>
<table xmlns:rev="http://www.cs.rpi.edu/~gregod/boost/tools/doc/revision" width="100%"><tr>
<td align="left"><p><small>Last revised: October 29, 2019 at 16:54:06 GMT</small></p></td>
<td align="left"><p><small>Last revised: March 23, 2020 at 21:06:56 GMT</small></p></td>
<td align="right"><div class="copyright-footer"></div></td>
</tr></table>
<hr>