forked from boostorg/range
*** empty log message ***
[SVN r24315]
This commit is contained in:
63
doc/portability.html
Executable file
63
doc/portability.html
Executable file
@@ -0,0 +1,63 @@
|
||||
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
|
||||
|
||||
<html>
|
||||
<head>
|
||||
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
|
||||
<title>Boost.Range Portability </title>
|
||||
<link rel="stylesheet" href="style.css" type="text/css">
|
||||
</head>
|
||||
|
||||
<body>
|
||||
|
||||
<table border="0" >
|
||||
<tr>
|
||||
<td ><img src="cboost.gif" border="0" ></td>
|
||||
<td ><h1 align="center">Boost.Range</h1></td>
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<h2>Portability</h2><a name="Portability" ></a>
|
||||
<p >
|
||||
Full support for built-in arrays require that the compiler supports class
|
||||
template partial specialization. For non-conforming compilers there might
|
||||
be a change that it works anyway thanks to workarounds in the type traits
|
||||
library. </p>
|
||||
<p >
|
||||
Notice that some compilers cannot do function template ordering properly. In
|
||||
that case one must rely of <code >result_iterator_of<></code> and a
|
||||
single function definition instead of
|
||||
overloaded versions for const and non-const arguments.
|
||||
|
||||
|
||||
So if one cares about old compilers, one should not pass rvalues
|
||||
to the functions.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
A huge effort has been made to port the library to as many compilers as
|
||||
possible. The results of the test-suites can be found
|
||||
<a href="http://boost.sourceforge.net/regression-logs/developer/range.html">here</a>.
|
||||
</p>
|
||||
|
||||
<hr>
|
||||
<p>
|
||||
(C) Copyright Thorsten Ottosen 2003-2004
|
||||
</p>
|
||||
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
<br>
|
||||
|
||||
|
||||
</body>
|
||||
</html>
|
||||
|
Reference in New Issue
Block a user