feedc0de/boost_function
1
0 Fork 0
forked from boostorg/function
Code Pull Requests Activity

Add a missing space.

Browse Source 
[SVN r11152]
This commit is contained in:
Darin Adler committed 2001-09-19 15:07:56 +00:00
1 parent b240e7efca
commit a30aa907d2
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
index.html
+1 -1
View File
@@ -56,7 +56,7 @@ And, of course, function pointers have several advantages over Boost.Function:
<p> With a properly inlining compiler, an invocation of a function object requires one call through a function pointer. If the call is to a free function pointer, an additional call must be made to that function pointer (unless the compiler has very powerful interprocedural analysis). <p> With a properly inlining compiler, an invocation of a function object requires one call through a function pointer. If the call is to a free function pointer, an additional call must be made to that function pointer (unless the compiler has very powerful interprocedural analysis).
<h2><a name="portability">Portability</a></h2> <h2><a name="portability">Portability</a></h2>
<p> The function object wrappers have been designed to be as portable as possible, and to support many compilers even when they do not support the C++ standard well. The following compilers have passed all of the testcases included with <code>boost::function</code>. <p> The function object wrappers have been designed to be as portable as possible, and to support many compilers even when they do not support the C++ standard well. The following compilers have passed all of the test cases included with <code>boost::function</code>.
<ul> <ul>
<li>GCC 2.95.3</li> <li>GCC 2.95.3</li>
<li>GCC 3.0</li> <li>GCC 3.0</li>