Index: libs/config/config.htm
===================================================================
RCS file: /cvsroot/boost/boost/libs/config/config.htm,v
retrieving revision 1.42
diff -u -r1.42 config.htm
--- libs/config/config.htm 15 Dec 2004 12:24:04 -0000 1.42
+++ libs/config/config.htm 27 Feb 2005 18:56:00 -0000
@@ -30,7 +30,7 @@
<a href="#Acknowledgements">Acknowledgements</a></pre>
<h2><a name="configuring"></a>Configuring Boost for Your Platform</h2>
<h4><a name="default_config"></a>Using the default boost configuration</h4>
- <p>Boost is comes already configured for most common compilers and platforms; you
+ <p>Boost comes already configured for most common compilers and platforms; you
should be able to use boost "as is". Since the compiler is configured
separately from the standard library, the default configuration should work
even if you replace the compiler's standard library with a third-party standard
@@ -71,10 +71,10 @@
running the boost configure script. From a shell command prompt you will need
to cd into <boost-root>/libs/config/ and type:</p>
<pre>sh ./configure</pre>
- <p>you will see a list of the items being checked as the script works it way
+ <p>You will see a list of the items being checked as the script works its way
through the regression tests. Note that the configure script only really
auto-detects your compiler if it's called g++, c++ or CC. If you are using some
- other compiler then you will need to set one or more of the following
+ other compiler, you will need to set one or more of the following
environment variables:</p>
<table border="1" cellpadding="7" cellspacing="1" width="624">
<tr>
@@ -103,11 +103,11 @@
<p>For example to run the configure script with HP aCC, you might use something
like:</p>
<pre>export CXX="aCC"
-export CXXFLAGS="-Aa
--DAportable -D__HPACC_THREAD_SAFE_RB_TREE -DRWSTD_MULTI_THREAD -DRW_MULTI_THREAD -D_REENTRANT -D_THREAD_SAFE" export LDFLAGS="-DAportable"
-export LIBS=
-"-lpthread" sh
-./configure</pre>
+export CXXFLAGS="-Aa -DAportable -D__HPACC_THREAD_SAFE_RB_TREE -DRWSTD_MULTI_THREAD -DRW_MULTI_THREAD \
+ -D_REENTRANT -D_THREAD_SAFE"
+export LDFLAGS="-DAportable"
+export LIBS="-lpthread"
+sh ./configure</pre>
<p>However you run the configure script, when it finishes you will find a new
header - user.hpp - located in the <boost-root/libs/config/> directory. <b><i>Note
that configure does not install this header into your boost include path by
@@ -123,11 +123,11 @@
committing a configure-modified user.hpp to the cvs repository (something you
will not be thanked for!).</p>
<p>Option 2: give the header a more memorable name, and place it somewhere
- convenient, then define the macro BOOST_USER_CONFIG to point to it. For example
+ convenient; then, define the macro BOOST_USER_CONFIG to point to it. For example
create a new sub-directory <boost-root>/boost/config/user/, and copy the
- header there; for example as "multithread-gcc-config.hpp". Then when compiling
+ header there; for example as "multithread-gcc-config.hpp". Then, when compiling,
add the command line option:
- -DBOOST_USER_CONFIG="boost/config/user/multithread-gcc-config.hpp", and boost
+ -DBOOST_USER_CONFIG="<boost/config/user/multithread-gcc-config.hpp>", and boost
will use the new configuration header. This option allows you to generate more
than one configuration header, and to keep them separate from the boost source
- so that updates to the source do not interfere with your configuration.</p>
@@ -1137,7 +1137,7 @@
</tr>
</table>
<h4><a name="info_macros"></a>Boost Informational Macros</h4>
- <p>The following macros describe boost features; these are the generally speaking
+ <p>The following macros describe boost features; these are, generally speaking,
the only boost macros that should be tested in user code.</p>
<table border="1" cellpadding="7" cellspacing="1" width="100%">
<tr>
@@ -1371,7 +1371,7 @@
<h4><a name="defect_guidelines"></a>Adding New Defect Macros</h4>
<p>When you need to add a new defect macro - either to fix a problem with an
existing library, or when adding a new library - distil the issue down to a
- simple test case, often at this point other (possibly better) workarounds may
+ simple test case; often, at this point, other (possibly better) workarounds may
become apparent. Secondly always post the test case code to the boost mailing
list and invite comments; remember that C++ is complex and that sometimes what
may appear a defect, may in fact turn out to be a problem with the authors
@@ -1463,7 +1463,7 @@
<p>Consider a situation in which you are concurrently developing on multiple
platforms. Then consider adding a new platform or changing the platform
definitions of an existing platform. What happens? Everything, and this does
- literally mean everything, recompiles.. Isn't it quite absurd that adding a new
+ literally mean everything, recompiles. Isn't it quite absurd that adding a new
platform, which has absolutely nothing to do with previously existing
platforms, means that all code on all existing platforms needs to be
recompiled?</p>
@@ -1494,8 +1494,8 @@
<p>The approach taken by boost's configuration headers is to separate
configuration into three orthogonal parts: the compiler, the standard library
and the platform. Each compiler/standard library/platform gets its own
- mini-configuration header, so that change to one compiler's configuration (for
- example) does not effect other compilers. In addition there are measures that
+ mini-configuration header, so that changes to one compiler's configuration (for
+ example) does not affect other compilers. In addition there are measures that
can be taken both to omit the compiler/standard library/platform detection code
(so that adding support to a new platform does not break dependencies), or to
freeze the configuration completely; providing almost complete protection
Index: libs/config/configure
===================================================================
RCS file: /cvsroot/boost/boost/libs/config/configure,v
retrieving revision 1.26
diff -u -r1.26 configure
--- libs/config/configure 13 Jan 2005 10:59:39 -0000 1.26
+++ libs/config/configure 27 Feb 2005 18:56:02 -0000
@@ -1257,7 +1257,7 @@
Note that this test script only gives an approximate
configuration - you will need to test the results carefully
-using the boost regresion test suite before using the results.
+using the boost regression test suite before using the results.
EOF
if test $enable_test = 'yes'; then
@@ -1265,8 +1265,8 @@
cat << EOF
This script reports only the difference between the detected
-configuration, and the existing boost configuration. It's
-primary aim is to quicky report how well boost is configured
+configuration, and the existing boost configuration. Its
+primary aim is to quickly report how well boost is configured
for one compiler.
***
@@ -3271,7 +3271,7 @@
cat << EEEOF
Adjustments to boost configuration have been written to
-user.hpp, copy this to boost/config/user.hpp to use "as is",
+user.hpp. Copy this to boost/config/user.hpp to use "as is",
or define BOOST_SITE_CONFIG to point to its location.
TREAT THIS FILE WITH CARE.
Index: libs/config/tools/configure.in
===================================================================
RCS file: /cvsroot/boost/boost/libs/config/tools/configure.in,v
retrieving revision 1.15
diff -u -r1.15 configure.in
--- libs/config/tools/configure.in 13 Jan 2005 10:59:43 -0000 1.15
+++ libs/config/tools/configure.in 27 Feb 2005 18:56:02 -0000
@@ -1,5 +1,5 @@
#
-# the following variable contain our macro diffs:
+# the following variables contain our macro diffs:
#
required_defs=""
required_undefs=""
@@ -25,7 +25,7 @@
Note that this test script only gives an approximate
configuration - you will need to test the results carefully
-using the boost regresion test suite before using the results.
+using the boost regression test suite before using the results.
EOF
if test $enable_test = 'yes'; then
@@ -33,8 +33,8 @@
cat << EOF
This script reports only the difference between the detected
-configuration, and the existing boost configuration. It's
-primary aim is to quicky report how well boost is configured
+configuration, and the existing boost configuration. Its
+primary aim is to quickly report how well boost is configured
for one compiler.
***
@@ -401,7 +401,7 @@
cat << EEEOF
Adjustments to boost configuration have been written to
-user.hpp, copy this to boost/config/user.hpp to use "as is",
+user.hpp. Copy this to boost/config/user.hpp to use "as is",
or define BOOST_SITE_CONFIG to point to its location.
TREAT THIS FILE WITH CARE.
@@ -415,29 +415,3 @@
)
fi
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
Index: libs/filesystem/doc/exception.htm
===================================================================
RCS file: /cvsroot/boost/boost/libs/filesystem/doc/exception.htm,v
retrieving revision 1.11
diff -u -r1.11 exception.htm
--- libs/filesystem/doc/exception.htm 5 Oct 2004 15:45:20 -0000 1.11
+++ libs/filesystem/doc/exception.htm 27 Feb 2005 18:56:02 -0000
@@ -125,7 +125,7 @@
appropriate:</p>
<ul>
<li>boost::filesystem::class-name::function-name for errors from public
- member functions</li>
+ member functions.</li>
<li>boost::filesystem::class-name for errors not identified with a
particular member function.</li>
<li>boost::filesystem::function-name for errors from non-member functions.</li>
@@ -203,4 +203,4 @@
</body>
-</html>
\ No newline at end of file
+</html>
Index: libs/filesystem/doc/faq.htm
===================================================================
RCS file: /cvsroot/boost/boost/libs/filesystem/doc/faq.htm,v
retrieving revision 1.14
diff -u -r1.14 faq.htm
--- libs/filesystem/doc/faq.htm 26 Feb 2005 01:58:30 -0000 1.14
+++ libs/filesystem/doc/faq.htm 27 Feb 2005 18:56:02 -0000
@@ -31,7 +31,7 @@
<p><b>Why do some function names have a "native_" prefix?</b></p>
<p>To alert users that the results are inherently non-portable. The names are
deliberately ugly to discourage use except where really necessary.</p>
-<p><b>Why not support a concept of specific kinds of file systems, such as posix_file_system or windows_file_system.</b></p>
+<p><b>Why not support a concept of specific kinds of file systems, such as posix_file_system or windows_file_system?</b></p>
<p>Portability is one of the one or two most important requirements for the
library. Gaining some advantage by using features specific to particular
operating systems is not a requirement. There doesn't appear to be much need for
Index: libs/iostreams/doc/classes/file_descriptor.html
===================================================================
RCS file: /cvsroot/boost/boost/libs/iostreams/doc/classes/file_descriptor.html,v
retrieving revision 1.2
diff -u -r1.2 file_descriptor.html
--- libs/iostreams/doc/classes/file_descriptor.html 14 Feb 2005 01:50:56 -0000 1.2
+++ libs/iostreams/doc/classes/file_descriptor.html 27 Feb 2005 18:56:03 -0000
@@ -39,7 +39,7 @@
</P>
<UL>
<LI CLASS="square">A file descriptor Device may be constructed from a file descriptor which is already open.
- <LI CLASS="square">The only buffering is provded by the Boost Iostreams Library.
+ <LI CLASS="square">The only buffering is provided by the Boost Iostreams Library.
<LI CLASS="square">There is no automatic line-endings conversion.
<LI CLASS="square">Wide-character streams are not supported.
</UL>
@@ -210,4 +210,4 @@
<!-- End Footer -->
-</BODY>
\ No newline at end of file
+</BODY>