|
|
Boost-Commit : |
Subject: [Boost-commit] svn:boost r48991 - in branches/bcbboost/libs: conversion python/doc python/doc/v2 spirit/doc/lex type_traits/doc utility
From: nicola.musatti_at_[hidden]
Date: 2008-09-28 17:23:57
Author: nmusatti
Date: 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
New Revision: 48991
URL: http://svn.boost.org/trac/boost/changeset/48991
Log:
Merge from trunk
Text files modified:
branches/bcbboost/libs/conversion/lexical_cast.htm | 6 +++---
branches/bcbboost/libs/python/doc/building.html | 2 +-
branches/bcbboost/libs/python/doc/v2/CallPolicies.html | 2 +-
branches/bcbboost/libs/spirit/doc/lex/lexer_quickstart3.qbk | 2 +-
branches/bcbboost/libs/spirit/doc/lex/tokens_values.qbk | 2 +-
branches/bcbboost/libs/type_traits/doc/credits.qbk | 2 +-
branches/bcbboost/libs/utility/operators.htm | 2 +-
7 files changed, 9 insertions(+), 9 deletions(-)
Modified: branches/bcbboost/libs/conversion/lexical_cast.htm
==============================================================================
--- branches/bcbboost/libs/conversion/lexical_cast.htm (original)
+++ branches/bcbboost/libs/conversion/lexical_cast.htm 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
@@ -81,7 +81,7 @@
conversions, such as where precision or formatting need tighter control than is
offered by the default behavior of <code>lexical_cast</code>, the conventional <code>
stringstream</code> approach is recommended. Where the conversions are
- numeric to numeric, <code>numeric_cast</code>
+ numeric to numeric, <code>numeric_cast</code>
may offer more reasonable behavior than <code>lexical_cast</code>.
<p>
For a good discussion of the options and issues involved in string-based
@@ -213,9 +213,9 @@
Lexical conversion to these types is simply reading a byte from source but since the source has
more than one byte, the exception is thrown.
<p>Please use other integer types such as <code>int</code> or <code>short int</code>. If bounds checking
- is important, you can also call numeric_cast:
+ is important, you can also call numeric_cast:
-<pre>numeric_cast<int8_t>(lexical_cast<int>("127"));</pre>
+<pre>numeric_cast<int8_t>(lexical_cast<int>("127"));</pre>
<p> Q: What does <code>lexical_cast<std::string></code> of an <code>int8_t</code> or <code>uint8_t</code> not do what I expect?
<br> A: As above, note that <code>int8_t</code> and <code>uint8_t</code> are actually chars and are formatted as such. To avoid this, cast to an integer type first:
Modified: branches/bcbboost/libs/python/doc/building.html
==============================================================================
--- branches/bcbboost/libs/python/doc/building.html (original)
+++ branches/bcbboost/libs/python/doc/building.html 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
@@ -9,7 +9,7 @@
</head>
<body>
<div class="document" id="logo-boost-python-build-and-test-howto">
-<h1 class="title"><a class="reference external" href="../index.htm"><img alt="Boost C++ Libraries:" class="boost-logo" src="../../../boost.png" /></a> Boost.Python Build and Test HOWTO</h1>
+<h1 class="title"><a class="reference external" href="../index.html"><img alt="Boost C++ Libraries:" class="boost-logo" src="../../../boost.png" /></a> Boost.Python Build and Test HOWTO</h1>
<!-- Copyright David Abrahams 2006. Distributed under the Boost -->
<!-- Software License, Version 1.0. (See accompanying -->
Modified: branches/bcbboost/libs/python/doc/v2/CallPolicies.html
==============================================================================
--- branches/bcbboost/libs/python/doc/v2/CallPolicies.html (original)
+++ branches/bcbboost/libs/python/doc/v2/CallPolicies.html 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
@@ -137,7 +137,7 @@
<td valign="top"><code>P::extract_return_type</code></td>
<td>A model of <a href=
- "../../../doc/refmanual/metafunction.html">Metafunction</a>.</td>
+ "../../../mpl/doc/refmanual/metafunction.html">Metafunction</a>.</td>
<td>An MPL unary <a href=
"../../../mpl/doc/refmanual/metafunction.html">Metafunction</a> used extract the return type from a given signature. By default it is derived from mpl::front.</td>
Modified: branches/bcbboost/libs/spirit/doc/lex/lexer_quickstart3.qbk
==============================================================================
--- branches/bcbboost/libs/spirit/doc/lex/lexer_quickstart3.qbk (original)
+++ branches/bcbboost/libs/spirit/doc/lex/lexer_quickstart3.qbk 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
@@ -20,7 +20,7 @@
library. The [link spirit.lex.flowcontrol picture] below shows the common
flow control implemented while parsing combined with lexical analysis.
-[fig ./images/FlowOfControl.png..The common flow control implemented while parsing combined with lexical analysis..spirit.lex.flowcontrol]
+[fig ./images/flowofcontrol.png..The common flow control implemented while parsing combined with lexical analysis..spirit.lex.flowcontrol]
Another problem related to the integration of the lexical analyzer with the
parser was to find a way how the defined tokens syntactically could be blended
Modified: branches/bcbboost/libs/spirit/doc/lex/tokens_values.qbk
==============================================================================
--- branches/bcbboost/libs/spirit/doc/lex/tokens_values.qbk (original)
+++ branches/bcbboost/libs/spirit/doc/lex/tokens_values.qbk 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
@@ -56,7 +56,7 @@
was matched in. The following [link spirit.lex.tokenstructure figure] shows the
schematic structure of a token.
-[fig ./images/TokenStructure.png..The structure of a token..spirit.lex.tokenstructure]
+[fig ./images/tokenstructure.png..The structure of a token..spirit.lex.tokenstructure]
The token value and the token state may be omitted for optimization reasons,
avoiding the token to carry more data than actually required. This
Modified: branches/bcbboost/libs/type_traits/doc/credits.qbk
==============================================================================
--- branches/bcbboost/libs/type_traits/doc/credits.qbk (original)
+++ branches/bcbboost/libs/type_traits/doc/credits.qbk 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
@@ -8,7 +8,7 @@
[section:credits Credits]
This documentation was pulled together by John Maddock, using
-[@../../../../tools/quickbook/doc/html/index.html Boost.Quickbook]
+[@../../../../doc/html/quickbook.html Boost.Quickbook]
and [@../../../../doc/html/boostbook.html Boost.DocBook].
The original version of this library was created by Steve Cleary,
Modified: branches/bcbboost/libs/utility/operators.htm
==============================================================================
--- branches/bcbboost/libs/utility/operators.htm (original)
+++ branches/bcbboost/libs/utility/operators.htm 2008-09-28 17:23:55 EDT (Sun, 28 Sep 2008)
@@ -2030,7 +2030,7 @@
</pre>
</blockquote>
- <p>Check the <a href="../../status/compiler_status.html">compiler status
+ <p>Check the <a href="http://www.boost.org/development/testing.html">compiler status
report</a> for the test results with selected platforms.</p>
<hr>
Boost-Commit list run by bdawes at acm.org, david.abrahams at rcn.com, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk