Boost-Commit :

Date view	Thread view	Subject view	Author view

From: bdawes_at_[hidden]
Date: 2008-03-18 15:35:19

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r43710 - in branches/release/libs/filesystem: doc example src"
Previous message: john_at_[hidden]: "[Boost-commit] svn:boost r43708 - website/public_html/beta/users"

Author: bemandawes
Date: 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
New Revision: 43709
URL: http://svn.boost.org/trac/boost/changeset/43709

Log:
Fix inspect boo boos; mostly broken links
Removed:
   trunk/libs/filesystem/example/vc++.bat
Text files modified:
   trunk/libs/filesystem/doc/do-list.htm | 5 +--
   trunk/libs/filesystem/doc/faq.htm | 8 -----
   trunk/libs/filesystem/doc/i18n.html | 32 ++++++++++++--------------
   trunk/libs/filesystem/doc/index.htm | 48 +++++++++++++++++++--------------------
   trunk/libs/filesystem/doc/reference.html | 7 ++---
   trunk/libs/filesystem/src/operations.cpp | 8 +++---
   6 files changed, 48 insertions(+), 60 deletions(-)

Modified: trunk/libs/filesystem/doc/do-list.htm
==============================================================================
--- trunk/libs/filesystem/doc/do-list.htm (original)
+++ trunk/libs/filesystem/doc/do-list.htm 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
@@ -4,8 +4,7 @@
Do-list</h1>
<h2>Current</h2>
<ul>
- <li>Add test cases and docs for Windows \\?\ and
- \\?\UNC\ naming conventions.</li>
+ <li>Add test cases and docs for Windows \\?\ and \\?\UNC\ naming conventions.</li>
 <li>Should operations.cpp assert or BOOST_ASSERT on more preconditions?</li>
 <li>Apply PJP's Wide/Narrow conversion proposal to traits, once he stabilizes it.</li>
 <li>Glob syntax -> regex syntax converter. See
@@ -35,7 +34,7 @@
</ul>
<hr>
Revised
-06 February, 2006
+18 March, 2008
© Copyright Beman Dawes, 2002
 Use, modification, and distribution are subject to the Boost Software
License, Version 1.0. (See accompanying file <a href="../../../LICENSE_1_0.txt">

Modified: trunk/libs/filesystem/doc/faq.htm
==============================================================================
--- trunk/libs/filesystem/doc/faq.htm (original)
+++ trunk/libs/filesystem/doc/faq.htm 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
@@ -141,15 +141,9 @@
basic_path member
functions, while operations performed by the operating system are provided as
free functions.
-Why is path normalized form different
-from canonical form?
-On operating systems such as POSIX which allow symbolic links to directories,
-the normalized form of a path can represent a different location than the
-canonical form. See use case
-from Walter Landry.
<hr>
Revised
-08 November, 2007
+18 March, 2008
© Copyright Beman Dawes, 2002
 Use, modification, and distribution are subject to the Boost Software
License, Version 1.0. See <a href="http://www.boost.org/LICENSE_1_0.txt">

Modified: trunk/libs/filesystem/doc/i18n.html
==============================================================================
--- trunk/libs/filesystem/doc/i18n.html (original)
+++ trunk/libs/filesystem/doc/i18n.html 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
@@ -37,8 +37,7 @@
 </li>
 <li>More efficient operations when iterating over directories. 
 </li>
- <li>A
- <a href="tr2_proposal.html#Class-template-basic_recursive_directory_iterator">recursive
+ <li>A <a href="reference.html#recursive_directory_iterator">recursive
 directory iterator</a> is now provided. </li>
</ul>
Rationale for some of the changes is also provided.
@@ -68,10 +67,10 @@
file systems the wpath external encoding is <a href="design.htm#Kuhn">
UTF-8</a>, while for modern Windows file systems such as NTFS it is
<a href="http://en.wikipedia.org/wiki/UTF-16">UTF-16</a>.
-The operational functions in
+The operational functions in
<a href="../../../boost/filesystem/operations.hpp">operations.hpp</a> are provided with overloads for
path, wpath, and user-defined basic_path's. A
-"do-the-right-thing" rule
+"do-the-right-thing" rule
applies to implementations, ensuring that the correct overload will be chosen.
<h2><a name="Simplification">Simplification</a> of path interface</h2>
Prior versions of the library required users of class path to identify
@@ -90,11 +89,10 @@
 it, but with much less impact on those who don't need it.</li>
</ul>
Additionally,
-basic_filesystem_error has been put
+basic_filesystem_error has been put
on a diet and generally simplified.
-Error codes have been simplified and aligned with [POSIX-01]. A supporting
-header <a href="../../../boost/filesystem/cerrno.hpp">
-<boost/filesystem/cerrno.hpp></a> is also provided.
+Error codes have been moved to a separate library,
+Boost.System.
<code>"//:"</code> has been introduced as a path escape prefix to identify
native paths. Rationale: simplifies basic_path constructor interfaces, easier
use for platforms needing explicit native format identification.
@@ -112,19 +110,19 @@
As part of the predicate discussions, particularly with Rob Stewart, it
became obvious that sometimes applications need access to raw status information
without any possibility of an exception being thrown. The
-status() function was added to meet this
+status() function was added to meet this
need. It also proved clearer to specify the semantics of predicate functions in
terms of status().
<h3><a name="is_file">is_file</a>()</h3>
About the same time, Jeff Garland suggested that an
-is_file() predicate would
-compliment is_directory(). In working on the analysis below, it became obvious
+is_file() predicate would
+compliment is_directory(). In working on the analysis below, it became obvious
that the expectations for is_file() were different from the expectations for !is_directory(),
so is_file() was added. 
<h3><a name="is_other">is_other</a>()</h3>
On some operating systems, it is possible to have a directory entry which is
not for either a directory or a file. The
-is_other()
+is_other()
function identifies such cases.
<h3>Should predicates throw on errors?</h3>
Some conditions reported by operating systems as errors (see
@@ -132,7 +130,7 @@
false, rather than indicating serious failure. But other errors represent
serious hardware or network problems, or permissions problems.
Some people, particularly Rob Stewart, argue that in a function like
-is_directory(), any error should simply cause the function to return false. If
+is_directory(), any error should simply cause the function to return false. If
there is actually an underlying problem, it will be detected it due course when
a directory_iterator or fstream operation is attempted.
That view is was rejected because of the following considerations:
@@ -390,7 +388,7 @@
 the problem worse. 
 </li>
</ul>
-<h3>No versions of status() which throw exceptions on
+<h3>No versions of status() which throw exceptions on
errors</h3>
The rationale for not including versions of status()
which throw exceptions on errors is that (1) the primary purpose of this
@@ -398,7 +396,7 @@
unwanted, and (2) exceptions on errors are already provided by the predicate
functions. There would be little or no efficiency gain from providing a throwing
version of status().
-<h3>Symlink identifying version of status() function</h3>
+<h3>Symlink identifying version of status() function</h3>
A symlink identifying version of the status() function is distinguished by a
second argument. Often separately named functions are more appropriate than
overloading when behavior
@@ -417,8 +415,8 @@
is also provided, to meet unforeseen needs.
<hr>
Revised
-03 June, 2007
-© Copyright Beman Dawes, 2005
+18 March, 2008
+Â© Copyright Beman Dawes, 2005
Distributed under the Boost Software License, Version 1.0.
(See accompanying file LICENSE_1_0.txt or
copy at www.boost.org/LICENSE_1_0.txt)

Modified: trunk/libs/filesystem/doc/index.htm
==============================================================================
--- trunk/libs/filesystem/doc/index.htm (original)
+++ trunk/libs/filesystem/doc/index.htm 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
@@ -128,12 +128,12 @@
using boost::filesystem; // for ease of tutorial presentation;
 // a namespace alias is preferred practice in real code</pre>
</blockquote>
-A class path object can be created:
+A class path object can be created:
<blockquote>
 <pre>path my_path( "some_dir/file.txt" );</pre>
</blockquote>
The string passed to the path constructor may be in a
-portable generic path format or an
+portable generic path format or an
implementation-defined native operating system format. Access functions
make my_path contents available to the underlying operating system API in an operating system dependent format,
such as <code>"some_dir:file.txt"</code>, <code>"[some_dir]file.txt"</code>,
@@ -166,7 +166,7 @@
Paths can include references to the current directory, using "<code>.</code>"
notation, and the parent directory, using "<code>..</code>"
notation.
-Class basic_directory_iterator
+Class basic_directory_iterator
is an important component of the library. It provides an input iterator over the
contents of a directory, with the value type being class basic_path.
Typedefs directory_iterator and wdirectory_iterator are provided
@@ -227,7 +227,7 @@
<h4>Effects and Postconditions not guaranteed in the presence of race-conditions</h4>
Filesystem function specifications follow the C++ Standard Library form, specifying behavior in terms of
effects and postconditions. If
-a race-condition exists, a function's
+a race-condition exists, a function's
postconditions may no longer be true by the time the function returns to the
caller.
<blockquote>
@@ -259,7 +259,7 @@
</blockquote>
<h4>May throw exceptions</h4>
Unless otherwise specified, Boost.Filesystem functions throw 
-basic_filesystem_error
+basic_filesystem_error
exceptions if they cannot successfully complete their operational
specifications. Also, implementations may use C++ Standard Library functions,
which may throw std::bad_alloc. These exceptions may be thrown even
@@ -292,10 +292,8 @@
The programs used to generate the Boost regression test status tables use the
Filesystem Library extensively.  See:
<ul>
- <li><a href="../../../tools/regression/process_jam_log.cpp">
- process_jam_log.cpp</a></li>
- <li><a href="../../../tools/regression/compiler_status.cpp">
- compiler_status.cpp</a></li>
+ <li>process_jam_log.cpp</li>
+ <li>compiler_status.cpp</li>
</ul>
Test programs are sometimes useful in understanding a library, as they
illustrate what the developer expected to work and not work. See:
@@ -498,12 +496,12 @@
 <li>Clearer specification, by reference to [POSIX-01],
 the ISO/IEEE Single Unix Standard, with provisions for Windows and other
 operating systems.</li>
- <li>New functions status,
- symlink_status,
- is_file,
- is_symlink,
- create_hard_link,
- create_symlink, path member and non-member swap, path inserter, path
+ <li>New functions status,
+ symlink_status,
+ is_file,
+ is_symlink,
+ create_hard_link,
+ create_symlink, path member and non-member swap, path inserter, path
 extractor, additional path relational and "/" operator overloads, additional
 path member template functions taking iterator arguments.</li>
 <li>More efficient operations when iterating over directories.</li>
@@ -522,19 +520,19 @@
<h3>Version 1.32.0</h3>

<ul>
- <li>file_size() function added.</li>
- <li>Class path relational operators added.</li>
- <li>equivalent() function added.</li>
- <li>create_directory() no longer
+ <li>file_size() function added.</li>
+ <li>Class path relational operators added.</li>
+ <li>equivalent() function added.</li>
+ <li>create_directory() no longer
 throws if the directory already exists. A bool is returned, indicating that
 the directory did not preexist. Similar changes made to
- create_directories().</li>
+ create_directories().</li>
 <li>Docs added for users wishing Cygwin/POSIX behavior
 on Windows.</li>
 <li>For POSIX, Large File Support (LSF) is enabled if available, such as on
 Linux.</li>
- <li>current_path() and
- initial_path() on POSIX now handle
+ <li>current_path() and
+ initial_path() on POSIX now handle
 very long paths correctly.</li>
</ul>

@@ -544,7 +542,7 @@
 <li>The object library can now be built for either
 static or dynamic (shared/dll) linking. </li>
 <li>Several added functions, including improved checking for directory and
- file name portability. See <a href="portability_guide.htm#name_checkÂ_functions">
+ file name portability. See <a href="portability_guide.htm#name_checkÃ‚Â_functions">
 Name check functions</a>.</li>
 <li>Separation of canonical form and normalized form and a new path member
 function normalize(). This changes behavior,
@@ -555,9 +553,9 @@

<hr>
Revised
-30 November, 2007
+18 March, 2008

-© Copyright Beman Dawes, 2002-2005
+Â© Copyright Beman Dawes, 2002-2005
 Use, modification, and distribution are subject to the Boost Software
License, Version 1.0. See <a href="http://www.boost.org/LICENSE_1_0.txt">
www.boost.org/LICENSE_1_0.txt</a>

Modified: trunk/libs/filesystem/doc/reference.html
==============================================================================
--- trunk/libs/filesystem/doc/reference.html (original)
+++ trunk/libs/filesystem/doc/reference.html 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
@@ -343,7 +343,7 @@

 template <class Path> class basic_recursive_directory_iterator;

- typedef basic_recursive_directory_iterator<path> recursive_directory_iterator;
+ typedef basic_recursive_directory_iterator<path> <a name="recursive_directory_iterator">recursive_directory_iterator</a>;
 typedef basic_recursive_directory_iterator<wpath> wrecursive_directory_iterator;

 enum file_type { status_unknown, file_not_found, regular_file, directory_file,
@@ -2260,8 +2260,7 @@
 be residue left over from a prior program run by the command
 processor! Although these semantics are often useful, they are also very
 error-prone.
- See
- <a href="file:///C|/boost/site/libs/filesystem/doc/operations.htm#complete_note">
+ See <a href="#complete_note">
 complete() note</a> for usage suggestions. -- end note]
</blockquote>
<h4><a name="Convenience-functions">Convenience functions</a></h4>
@@ -3058,7 +3057,7 @@
Distributed under the Boost Software License, Version 1.0. See
<a href="http://www.boost.org/LICENSE_1_0.txt">www.boost.org/LICENSE_1_0.txt</a>
Revised
-14 November 2007
+18 March 2008

</body>

Deleted: trunk/libs/filesystem/example/vc++.bat
==============================================================================
--- trunk/libs/filesystem/example/vc++.bat 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
+++ (empty file)
@@ -1,5 +0,0 @@
-set BOOST_ROOT=..\..\..
-rem A more robust script would test for BOOST_ROOT already set in the environment.
-
-cl -EHsc -I%BOOST_ROOT% %* -link -LIBPATH:%BOOST_ROOT%\lib
-

Modified: trunk/libs/filesystem/src/operations.cpp
==============================================================================
--- trunk/libs/filesystem/src/operations.cpp (original)
+++ trunk/libs/filesystem/src/operations.cpp 2008-03-18 15:35:18 EDT (Tue, 18 Mar 2008)
@@ -1319,12 +1319,12 @@
         if ( result == 0 ) return dir_itr_close( handle, buffer );
         target = entry->d_name;
# ifdef BOOST_FILESYSTEM_STATUS_CACHE
- if ( entry->d_type == DT_UNKNOWN ) // filesystem does not supply d_type value
+ if ( entry->d_type == DT_UNKNOWN ) // filesystem does not supply d_type value
         {
           sf = symlink_sf = fs::file_status(fs::status_unknown);
         }
- else // filesystem supplies d_type value
- {
+ else // filesystem supplies d_type value
+ {
           if ( entry->d_type == DT_DIR )
             sf = symlink_sf = fs::file_status( fs::directory_file );
           else if ( entry->d_type == DT_REG )
@@ -1335,7 +1335,7 @@
             symlink_sf = fs::file_status( fs::symlink_file );
           }
           else sf = symlink_sf = fs::file_status( fs::status_unknown );
- }
+ }
# else
         sf = symlink_sf = fs::file_status( fs::status_unknown );
# endif

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r43710 - in branches/release/libs/filesystem: doc example src"
Previous message: john_at_[hidden]: "[Boost-commit] svn:boost r43708 - website/public_html/beta/users"

Date view	Thread view	Subject view	Author view

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