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

fix broken link

Browse Source 
[SVN r20964]
This commit is contained in:
Beman Dawes
2003-11-26 18:11:45 +00:00
parent cec4768110
commit 2f95ee89df
1 changed files with 4 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
config.htm
View File

@@ -96,7 +96,7 @@ export LDFLAGS="-DAportable"
export LIBS="-lpthread" export LIBS="-lpthread"
./configure</pre> ./configure</pre>
<p>However you run the configure script, when it finishes you will find a new <p>However you run the configure script, when it finishes you will find a new
header - user.hpp - located in the <a href="user.hpp">&lt;boost-root&gt;/libs/config/</a> header - user.hpp - located in the &lt;boost-root/libs/config/&gt;
directory. <b><i>Note that configure does not install this header into your boost directory. <b><i>Note that configure does not install this header into your boost
include path by default.</i></b> This header contains all the options include path by default.</i></b> This header contains all the options
generated by the configure script, plus a header-section that contains the user generated by the configure script, plus a header-section that contains the user
@@ -965,8 +965,7 @@ void g() { return f(); }</pre>
incorrectly outputs <tt>"2 2 double double "</tt> on VC++ 6. These macros, to incorrectly outputs <tt>"2 2 double double "</tt> on VC++ 6. These macros, to
be used in the function parameter list, fix the problem without effects on the be used in the function parameter list, fix the problem without effects on the
calling syntax. For instance, in the case above write: calling syntax. For instance, in the case above write:
<pre> <pre> template &lt;int n&gt;
template &lt;int n&gt;
void f(BOOST_EXPLICIT_TEMPLATE_NON_TYPE(int, n)) { ... } void f(BOOST_EXPLICIT_TEMPLATE_NON_TYPE(int, n)) { ... }
template &lt;typename T&gt; template &lt;typename T&gt;
@@ -1117,8 +1116,7 @@ void g() { return f(); }</pre>
declared in your library, in order to avoid sprinkling #pragma's all over the declared in your library, in order to avoid sprinkling #pragma's all over the
boost headers, there are some prefix and suffix headers that do the job, boost headers, there are some prefix and suffix headers that do the job,
typical usage would be:</P> typical usage would be:</P>
<PRE> <PRE>#ifndef MY_INCLUDE_GUARD
#ifndef MY_INCLUDE_GUARD
#define MY_INCLUDE_GUARD #define MY_INCLUDE_GUARD
// all includes go here: // all includes go here: