Boost-Commit :

Date view	Thread view	Subject view	Author view

Subject: [Boost-commit] svn:boost r59126 - sandbox/filesystem-v3/libs/filesystem/doc
From: bdawes_at_[hidden]
Date: 2010-01-18 09:48:51

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r59127 - website/public_html/beta/community"
Previous message: strasser_at_[hidden]: "[Boost-commit] svn:boost r59125 - sandbox/transaction/dev"

Author: bemandawes
Date: 2010-01-18 09:48:50 EST (Mon, 18 Jan 2010)
New Revision: 59126
URL: http://svn.boost.org/trac/boost/changeset/59126

Log:
Fix broken and dup links. Update FAQ
Text files modified:
   sandbox/filesystem-v3/libs/filesystem/doc/do_list.html | 11 ++
   sandbox/filesystem-v3/libs/filesystem/doc/faq.htm | 46 ++++--------
   sandbox/filesystem-v3/libs/filesystem/doc/index.htm | 4
   sandbox/filesystem-v3/libs/filesystem/doc/reference.html | 147 ++++++++++++++++++---------------------
   4 files changed, 95 insertions(+), 113 deletions(-)

Modified: sandbox/filesystem-v3/libs/filesystem/doc/do_list.html
==============================================================================
--- sandbox/filesystem-v3/libs/filesystem/doc/do_list.html (original)
+++ sandbox/filesystem-v3/libs/filesystem/doc/do_list.html 2010-01-18 09:48:50 EST (Mon, 18 Jan 2010)
@@ -23,7 +23,6 @@
 <li>Reorganize files</li>
 <li>Fix broken links.</li>
 <li>Create Jamfile for examples</li>
- <li>Review FAQ.</li>
 <li>Review Index.html</li>
 <li>Should minimal.css be changed to used relative font sizes? See
 <a href="http://www.w3schools.com/CSS/pr_font_font-size.asp/">http://www.w3schools.com/CSS/pr_font_font-size.asp\</a></li>
@@ -81,8 +80,18 @@
 <li>Two argument recursive_directory_iterator ctor isn't recognizing throws().
 Would it be better to fold into a single two argument ctor with default?</li>
 <li>Add the push_directory class from tools/release/required_files.cpp</li>
+ <li>directory_entry needs relational operators?</li>
</ul>

+<hr>
+© Copyright Beman Dawes, 2010
+Distributed under the Boost Software License, Version 1.0. See
+www.boost.org/LICENSE_1_0.txt
+Revised
+18 January 2010
+
+ 
+
</body>

</html>
\ No newline at end of file

Modified: sandbox/filesystem-v3/libs/filesystem/doc/faq.htm
==============================================================================
--- sandbox/filesystem-v3/libs/filesystem/doc/faq.htm (original)
+++ sandbox/filesystem-v3/libs/filesystem/doc/faq.htm 2010-01-18 09:48:50 EST (Mon, 18 Jan 2010)
@@ -36,20 +36,15 @@
<h2>General questions</h2>
Why not support a concept of specific kinds of file systems, such as posix_file_system or windows_file_system.
Portability is one of the 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
-the ability to manipulate, say, a classic Mac OS path while running on an
-OpenVMS machine.
-Furthermore, concepts like "file system"
-are very slippery. What happens when a NTFS or FAT file system is mounted
-in directory on a machine running a POSIX-like operating system, for example?
-Some of the POSIX API's may return very un-POSIX like results.
+library. Features specific to a particular operating system or file system
+can always be accessed by using the operating system's API.

<h2 dir="ltr">
Class <code>path</code> questions </h2>
-Why base the generic-path string format on POSIX?
-[POSIX-01] is an ISO Standard. It is the basis for the most familiar path-string formats,
-not just for POSIX systems but also for the native Windows format and the
+Why base the generic pathname format on POSIX?
+POSIX is an ISO Standard. It is the basis for the most familiar
+pathname formats,
+not just for POSIX-based operating systems but also for Windows and the
URL portion of URI's. It is ubiquitous and
familiar.  On many systems, it is very easy to implement because it is
either the native operating system format (Unix and Windows) or via a
@@ -64,7 +59,7 @@
file_path classes?
Why bother?  The behavior of all three classes is essentially identical.
Several early versions did require users to identify each path as a file or
-directory path, and this seemed to increase errors and decrease code
+directory path, and this seemed to increase coding errors and decrease code
readability. There was no apparent upside benefit.
Why do path decomposition functions yielding a single element return a
path rather than a string?
@@ -98,10 +93,10 @@
toolkit functions.  See <a href="design.htm#Abandoned_Designs">Failed
Attempts</a>.
Isn't it inconsistent then to provide a few convenience functions?
-Yes, but experience with both this library, POSIX, and Windows indicates
+Yes, but experience with both this library, POSIX, and Windows, indicates
the utility of certain convenience functions, and that it is possible to provide
-simple, yet widely acceptable, semantics for them. For example, remove_all.
-Why are there basic_directory_iterator<> overloads for operations.hpp
+simple, yet widely acceptable, semantics for them. For example, <code>remove_all()</code>.
+Why are there directory_iterator overloads for operations.hpp
predicate functions? Isn't two ways to do the same thing poor design?
Yes, two ways to do the same thing is often a poor design practice. But the
iterator versions are often much more efficient. Calling status() during
@@ -110,18 +105,11 @@
machine. Times were .90 seconds and .30 seconds, for tests after prior use of
the directory. This performance gain is large enough to justify deviating from
preferred design practices. Neither overload alone meets all needs.
-Why are library functions so picky about errors?
+Why are the operations functions so picky about errors?
Safety. The default is to be safe rather than sorry. This is particularly
important given the reality that on many computer systems files and directories
-are globally shared resources, and thus subject to
-unexpected errors.
-Why are errors reported by exception rather than return code or error
-notification variable?
-Safety. Return codes or error notification variables are often ignored
-by programmers.  Exceptions are much harder to ignore, provided desired
-default behavior (program termination) if not caught, yet allow error recovery
-if desired. Non-throwing versions of functions are provided where experience
-indicates the need.
+are globally shared resources, and thus subject to
+race conditions.
Why are attributes accessed via named functions rather than property maps?
For commonly used attributes (existence, directory or file, emptiness),
simple syntax and guaranteed presence outweigh other considerations. Because
@@ -130,10 +118,6 @@
better design to provide such functionality in a separate library. (Historical
note: even the apparently simple attribute "read-only" turned out to be so
system depend as to be disqualified as a "guaranteed presence" operation.)
-Why aren't <a name="wide-character_names">wide-character names</a> supported? Why not std::wstring or even
-a templated type?
-They are supported, starting with version 1.33. See
-Internationalization.
Why isn't automatic name portability error detection provided?
A number (at least six) of designs for name validity error
detection were evaluated, including at least four complete implementations. 
@@ -145,12 +129,12 @@
Why are paths sometimes manipulated by member functions and sometimes by
non-member functions?
The design rule is that purely lexical operations are supplied as class
-basic_path member
+path member
functions, while operations performed by the operating system are provided as
free functions.
<hr>
Revised
-03 January, 2010
+18 January, 2010
© 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: sandbox/filesystem-v3/libs/filesystem/doc/index.htm
==============================================================================
--- sandbox/filesystem-v3/libs/filesystem/doc/index.htm (original)
+++ sandbox/filesystem-v3/libs/filesystem/doc/index.htm 2010-01-18 09:48:50 EST (Mon, 18 Jan 2010)
@@ -64,7 +64,7 @@
 <a href="design.htm">Library Design</a> 
 <a href="faq.htm">FAQ</a> 
 <a href="portability_guide.htm">Portability Guide</a> 
- Do-list
+ Do-list
 </td>
 </tr>
</table>
@@ -802,7 +802,7 @@

<hr>
Revised
-22 December, 2009
+17 January, 2010

© Copyright Beman Dawes, 2002-2005
 Use, modification, and distribution are subject to the Boost Software

Modified: sandbox/filesystem-v3/libs/filesystem/doc/reference.html
==============================================================================
--- sandbox/filesystem-v3/libs/filesystem/doc/reference.html (original)
+++ sandbox/filesystem-v3/libs/filesystem/doc/reference.html 2010-01-18 09:48:50 EST (Mon, 18 Jan 2010)
@@ -39,29 +39,27 @@

<h1>Reference Documentation</h1>

-dummy
-
<h2><a name="TOC">Table of Contents</a></h2>

<table border="0" cellpadding="0" cellspacing="0" style="border-collapse: collapse" bordercolor="#111111" width="100%">
 <tr>
 <td width="33%" valign="top">Introduction 
 <a href="#Definitions">Definitions</a> 
+ Conformance 
 <a href="#Header-filesystem-synopsis">
 Header <filesystem> synopsis</a> 
 <a href="#Error-reporting">Error reporting</a> 
 <a href="#class-path">Class path</a> 
-    
-Pathname formats 
-    
-Pathname grammar 
-    
-Filename conversion 
     path constructors 
    path assignments 
    path appends 
    path modifiers 
-    path observers 
+    <a href="#path-native-format-observers">path native
+ format observers</a> 
+    <a href="#path-generic-format-observers">path generic
+ format observers</a> 
+    path decomposition 
+    path query 
    path iterators 
    path deprecated functions 
    path non-member functions 
@@ -77,7 +75,6 @@
<a href="#directory_entry-constructors">directory_entry constructors</a> 
    directory_entry modifiers 
    directory_entry observers 
-    directory_entry comparisons 
<a href="#Class-directory_iterator">Class directory_iterator</a> 
    <a href="#directory_iterator-members">directory_iterator
 members</a> 
@@ -155,7 +152,7 @@
<a name="Path">Path</a>: A sequence of elements that identify
a location within a filesystem. The elements are the root-nameopt, 
root-directoryopt, and an optional sequence of filenames. [Note:
-A pathname is the concrete representation of a path. --end note]
+A pathname is the concrete representation of a path. --end note]
<a name="Absolute-path">Absolute path</a>: A path that uniquely
identifies a file. The format is implementation defined. 
<blockquote>
@@ -287,7 +284,7 @@
 {
 namespace filesystem
 {
- class path;
+ class path;

 void swap(path& lhs, path& rhs);
 bool lexicographical_compare(path::iterator first1, path::iterator last1,
@@ -364,9 +361,9 @@
 void current_path(const path& p);
 void current_path(const path& p, system::error_code& ec);

- bool exists(file_status s);
- bool exists(const path& p);
- bool exists(const path& p, system::error_code& ec);
+ bool exists(file_status s);
+ bool exists(const path& p);
+ bool exists(const path& p, system::error_code& ec);

 bool equivalent(const path& p1, const path& p2);
 bool equivalent(const path& p1, const path& p2, system::error_code& ec);
@@ -534,7 +531,7 @@
 path& replace_extension(const path& new_extension = path());
 path& localize(); // POSIX: no effect. Windows: convert slashes to backslashes

- // native format observers
+ // native format observers
 const string_type& native() const; // native format, encoding
 const value_type* c_str() const; // native().c_str()

@@ -546,7 +543,7 @@
 const u16string u16string() const; // ditto
 const u32string u32string() const; // ditto

- // generic format observers
+ // generic format observers
 template <class String>
 String generic_string() const;

@@ -634,7 +631,7 @@
 wchar_t</code>, <code>char16_t</code>, or <code>char32_t</code>.</li>
 <li>A <code>boost::filesystem::directory_entry</code>.</li>
</ul>
-Iteration over <code><a name="ContiguousIterator">ContiguousIterator</a></code>
+Iteration over <code>ContiguousIterator</code>
and <code>Source</code> arguments shall result in generic pathname format or
native pathname format strings.
The specifications for certain <code>path</code> functions require that
@@ -719,8 +716,7 @@
 or <code>source</code> is not <code>value_type</code>, the contents are
 converted by <code>codecvt()</code>.
 </blockquote>
-<h3> <code> <a name="path-appends">path</a></code><a name="path-appends">
-appends</a></h3>
+<h3> <a name="path-appends"><code> path</code> appends</a></h3>
 The append operations use <code>operator/=</code> to denote their semantic
 effect of appending the platform's preferred directory separator when needed. The
 preferred
@@ -817,9 +813,10 @@
 Returns: <code>*this</code>
</blockquote>

-<h3><code>path</code> <a name="path-native-format-observers">
-native format</a><a name="path-native-format-observers"> observers</a></h3>
-The string returned by all native format observers is in the native pathname format.
+<h3> <a name="path-native-format-observers"><code>path</code>
+native format observers</a></h3>
+The string returned by all native format observers is in the
+native pathname format.
<pre>const string_type& native() const;</pre>
<blockquote>
Returns: <code>pathname</code>.
@@ -852,9 +849,8 @@
<code>string()</code>, for Windows, <code>wstring()</code>. --end note]
</blockquote>

-<h3><code>path</code>
-<a name="path-generic-format-observers">generic format</a><a name="path-native-format-observers">
-observers</a></h3>
+<h3> <a name="path-generic-format-observers"><code>path</code>
+generic format observers</a></h3>
The string returned by all generic format observers is in the
<a href="#generic-pathname-format">generic pathname format</a>.
[Note: For POSIX, no conversion occurs, since the native format and
@@ -1020,8 +1016,7 @@
<blockquote>
 Returns: The end iterator.
</blockquote>
-<h3> <code> <a name="path-deprecated-functions">path</a></code><a name="path-deprecated-functions">
-deprecated functions</a></h3>
+<h3> <a name="path-deprecated-functions"><code> path</code> deprecated functions</a></h3>
 index.htm
also has a section (see macros) partially duplicating this material. Change to
reference this.
@@ -1110,8 +1105,7 @@
 representations only. Thus <code>path("foo") == "bar"</code> is never
 <code>true</code>.
 Equivalence is determined by the equivalent()
- non-member function, which determines if two paths
- resolve to the same file system entity.
+ non-member function, which determines if two paths resolve to the same file system entity.
 Thus <code>equivalent("foo", "bar")</code> will be <code>true</code>
 when both paths resolve to the same file.
 Programmers wishing to determine if two paths are "the same" must decide if
@@ -1693,8 +1687,8 @@
 Returns: <code>m_no_push_request</code>.
 Throws: Nothing.
</blockquote>
-<pre><code>recursive_</code>directory_iterator& <a name="directory_iterator-increment">operator++</a>();
-<code>recursive_</code>directory_iterator& increment(system::error_code& ec);</pre>
+<pre><code>recursive_directory_iterator</code>& <a name="recursive_directory_iterator-increment">operator++</a>();
+recursive_directory_iterator& increment(system::error_code& ec);</pre>
<blockquote>

Effects: As specified by the C++ Standard, 24.1.1 Input iterators [input.iterators],
@@ -1844,7 +1838,7 @@

</blockquote>
<pre>void <a name="copy_file">copy_file</a>(const path& from, const path& to, BOOST_SCOPED_ENUM(copy_option) option);
-void <a name="copy_file">copy_file</a>(const path& from, const path& to, BOOST_SCOPED_ENUM(copy_option) option, system::error_code& ec);</pre>
+void <a name="copy_file2">copy_file</a>(const path& from, const path& to, BOOST_SCOPED_ENUM(copy_option) option, system::error_code& ec);</pre>
<blockquote>
 Effects: If <code>option == copy_option::</code><code>fail_if_exists
 && exists(to)</code>, an error is reported. Otherwise, the contents and attributes of the file <code>from</code>
@@ -1854,7 +1848,7 @@
 Error reporting</a>.
</blockquote>
<pre>bool <a name="create_directories">create_directories</a>(const path& p);
-bool <a name="create_directories">create_directories</a>(const path& p, system::error_code& ec);</pre>
+bool <a name="create_directories2">create_directories</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Requires: <code>p.empty() || 
 forall px: px == p || is_parent(px, p): is_directory(px) || !exists( px )</code>
@@ -1867,7 +1861,7 @@
 Error reporting</a>.
</blockquote>
<pre>bool <a name="create_directory">create_directory</a>(const path& p);
-bool <a name="create_directory">create_directory</a>(const path& p, system::error_code& ec);</pre>
+bool <a name="create_directory2">create_directory</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Effects: Attempts to create the directory <code>p</code> resolves to,
 as if by POSIX <code>
@@ -1880,7 +1874,7 @@
 Error reporting</a>.
</blockquote>
<pre>void <a name="create_hard_link">create_hard_link</a>(const path& to, const path& from);
-void <a name="create_hard_link">create_hard_link</a>(const path& to, const path& from, system::error_code& ec);</pre>
+void <a name="create_hard_link2">create_hard_link</a>(const path& to, const path& from, system::error_code& ec);</pre>
<blockquote>
 Effects: Establishes the postcondition, as if by
 POSIX
@@ -1907,7 +1901,7 @@
 situations are not concerns, or if workarounds are provided. -- end note]
 </blockquote>
<pre>void <a name="create_symlink">create_symlink</a>(const path& to, const path& from);
-void <a name="create_symlink">create_symlink</a>(const path& to, const path& from, system::error_code& ec);</pre>
+void <a name="create_symlink2">create_symlink</a>(const path& to, const path& from, system::error_code& ec);</pre>
<blockquote style="font-size: 10pt">
 Effects:
 Establishes the postcondition, as if by 
@@ -1933,7 +1927,7 @@
 not concerns, or if workarounds are provided. -- end note]
 </blockquote>
<pre>path <a name="current_path">current_path</a>();
-path <a name="current_path">current_path</a>(system::error_code& ec);</pre>
+path <a name="current_path2">current_path</a>(system::error_code& ec);</pre>
<blockquote>
 Returns: The current working directory path, as if by POSIX
 <code>
@@ -1963,14 +1957,14 @@
<a href="#Error-reporting">
Error reporting</a>.
</blockquote>
-<pre>bool <a name="exists-file_status">exists</a>(file_status s);</pre>
+<pre>bool <a name="exists">exists</a>(file_status s);</pre>
<blockquote>
 Returns:
 <code>status_known(s) && s.type() != file_not_found</code>
 Throws: Nothing.
</blockquote>
-<pre>bool <a name="exists-path">exists</a>(const path& p);
-bool <a name="exists2">exists</a>(const path& p, system::error_code& ec);</pre>
+<pre>bool <a name="exists2">exists</a>(const path& p);
+bool <a name="exists3">exists</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Returns: <code>exists(status(p))</code> or <code>exists(status(p, ec))</code>,
 respectively.
@@ -1978,7 +1972,7 @@
nothing.
</blockquote>
<pre><code>bool <a name="equivalent">equivalent</a>(const path& p1, const path& p2);
-bool <a name="equivalent">equivalent</a>(const path& p1, const path& p2, system::error_code& ec);</code></pre>
+bool <a name="equivalent2">equivalent</a>(const path& p1, const path& p2, system::error_code& ec);</code></pre>
<blockquote style="font-size: 10pt">
 Effects: Determines <code>file_status s1</code>
 and <code>s2</code>, as if by <code>status(p1)</code> and  <code>status(p2)</code>,
@@ -2013,7 +2007,7 @@
 Error reporting</a>.
</blockquote>
<pre>uintmax_t <a name="file_size">file_size</a>(const path& p);
-uintmax_t <a name="file_size">file_size</a>(const path& p, system::error_code& ec);</pre>
+uintmax_t <a name="file_size2">file_size</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Remarks: 
 Returns: If <code>exists(p) && is_regular_file(p)</code>, the size
@@ -2029,7 +2023,7 @@
 Error reporting</a>.
</blockquote>
<pre>const path& <a name="initial_path">initial_path</a>();
-const path& <a name="initial_path">initial_path</a>(system::error_code& ec);</pre>
+const path& <a name="initial_path2">initial_path</a>(system::error_code& ec);</pre>
<blockquote>
 Returns: <code>current_path()</code> at the time of entry to <code>
 main()</code>.
@@ -2039,9 +2033,9 @@
 [Note: Full implementation requires runtime library support.
 Implementations which cannot provide runtime library support are encouraged to
 instead store the value of <code>current_path()</code> at the first call of
- <a name="initial_path"><code>initial_path</code></a><code>()</code>, and
+ <code>initial_path</code><code>()</code>, and
 return this value for all subsequent calls. Programs using
- <a name="initial_path"><code>initial_path</code></a><code>()</code> are
+ <code>initial_path</code><code>()</code> are
 encouraged to call it immediately on entrance to <code>main()</code> so that
 they will work correctly with such partial implementations. --end note]
</blockquote>
@@ -2052,25 +2046,22 @@
 Throws: Nothing.
</blockquote>
<pre><code>bool <a name="is_directory2">is_directory</a>(const path& p);
-bool <a name="is_directory2">is_directory</a>(const path& p, system::error_code& ec);</code></pre>
+bool <a name="is_directory3">is_directory</a>(const path& p, system::error_code& ec);</code></pre>
<blockquote>
- Returns: <code>is_<a name="is_directory2">directory</a>(status(p))</code> or <code>is_directory(status(p, ec))</code>,
+ Returns: <code>is_directory(status(p))</code> or <code>is_directory(status(p, ec))</code>,
 respectively.
Throws: <code>filesystem_error</code>; overload with <code>error_code&</code> throws
nothing.
</blockquote>
-<pre><code>bool <a name="is_empty">is_</a><a name="is_empty">empty</a>(const path& p);
-bool <a name="is_empty">is_</a><a name="is_empty">empty</a>(const path& p, system::error_code& ec);</code></pre>
+<pre><code>bool <a name="is_empty">is_empty</a>(const path& p);
+bool <a name="is_empty2">is_empty</a></a>(const path& p, system::error_code& ec);</code></pre>
<blockquote>
- Effects: Determines
- <code>file_status s</code>, as if by
- <code>
- status(p, ec)</code>.
- Returns:
- <code>is_directory(s) 
+ Effects: Determines <code>file_status s</code>, as if by <code>
+ status(p, ec)</code>.
+ Returns: <code>is_directory(s) 
         ?
 directory_iterator(p) == directory_iterator() 
-         : file_size(p) == 0;</code>
+         : file_size(p) == 0;</code>
</blockquote>
<pre>bool <code><a name="is_regular_file">is_regular_file</a></code>(file_status s);</pre>
<blockquote>
@@ -2084,7 +2075,7 @@
 Throws: <code>filesystem_error</code>
 if <code>status(p)</code> would throw <code>filesystem_error.</code>
 </blockquote>
-<pre><code>bool <a name="is_regular_file2">is_regular_file</a>(const path& p, system::error_code& ec);</code></pre>
+<pre><code>bool <a name="is_regular_file3">is_regular_file</a>(const path& p, system::error_code& ec);</code></pre>
<blockquote>
 Effects: Sets <code>ec</code> as if by <code>status(p, ec)</code>.
 [Note:
@@ -2109,7 +2100,7 @@
 Throws: Nothing.
</blockquote>
<pre><code>bool <a name="is_other2">is_other</a>(const path& p);
-bool <a name="is_other2">is_other</a>(const path& p, system::error_code& ec);</code></pre>
+bool <a name="is_other3">is_other</a>(const path& p, system::error_code& ec);</code></pre>
<blockquote>
 Returns: <code>is_other(status(p))</code> or <code>is_other(status(p, ec))</code>,
 respectively.
@@ -2123,7 +2114,7 @@
 Throws: Nothing.
</blockquote>
<pre><code>bool <a name="is_symlink2">is_symlink</a>(const path& p);
-bool <a name="is_symlink2">is_symlink</a>(const path& p, system::error_code& ec);</code></pre>
+bool <a name="is_symlink3">is_symlink</a>(const path& p, system::error_code& ec);</code></pre>
<blockquote>
 Returns: <code>is_symlink(symlink_status(p))</code> or <code>is_symlink(symlink_status(p, ec))</code>,
 respectively.
@@ -2131,7 +2122,7 @@
 nothing.
</blockquote>
<pre>std::time_t <a name="last_write_time">last_write_time</a>(const path& p);
-std::time_t <a name="last_write_time">last_write_time</a>(const path& p<code>, system::error_code& ec</code>);</pre>
+std::time_t <a name="last_write_time2">last_write_time</a>(const path& p<code>, system::error_code& ec</code>);</pre>
<blockquote>
 Returns: The time of last data modification of <code>p</code>, determined as if by the
 value of the POSIX <code>
@@ -2139,8 +2130,8 @@
 as if by POSIX <code>
 <a href="http://www.opengroup.org/onlinepubs/000095399/functions/stat.html">stat()</a></code>.
</blockquote>
-<pre>void <a name="last_write_time2">last_write_time</a>(const path& p, const std::time_t new_time);
-void <a name="last_write_time2">last_write_time</a>(const path& p, const std::time_t new_time<code>, system::error_code& ec</code>);</pre>
+<pre>void <a name="last_write_time3">last_write_time</a>(const path& p, const std::time_t new_time);
+void <a name="last_write_time4">last_write_time</a>(const path& p, const std::time_t new_time<code>, system::error_code& ec</code>);</pre>
<blockquote>
 Effects: Sets the time of last data modification of the file
 resolved to by <code>p</code>
@@ -2168,7 +2159,7 @@
 resolve to a symbolic link. -- end note]
</blockquote>
<pre>bool <a name="remove">remove</a>(const path& p);
-bool <a name="remove">remove</a>(const path& p, system::error_code& ec);</pre>
+bool <a name="remove2">remove</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Effects:  If <code>exists(symlink_status(p,ec))</code>, it is
 removed
@@ -2186,7 +2177,7 @@
 Error reporting</a>.
</blockquote>
<pre>uintmax_t <a name="remove_all">remove_all</a>(const path& p);
-uintmax_t <a name="remove_all">remove_all</a>(const path& p, system::error_code& ec);</pre>
+uintmax_t <a name="remove_all2">remove_all</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Effects:  Recursively deletes the contents of p if it exists,
 then deletes file <code>p</code> itself,
@@ -2203,7 +2194,7 @@
 Error reporting</a>.
</blockquote>
<pre>void <a name="rename">rename</a>(const path& old_p, const path& new_p);
-void <a name="rename">rename</a>(const path& old_p, const path& new_p, system::error_code& ec);</pre>
+void <a name="rename2">rename</a>(const path& old_p, const path& new_p, system::error_code& ec);</pre>
<blockquote>
 Effects: Renames <code>old_p</code> to <code>new_p</code>, as if by
 POSIX <code>
@@ -2221,7 +2212,7 @@
 Error reporting</a>.
</blockquote>
<pre>void <a name="resize_file">resize_file</a>(const path& p, uintmax_t new_size);
-void <a name="resize_file">resize_file</a>(const path& p, uintmax_t new_size, system::error_code& ec);</pre>
+void <a name="resize_file2">resize_file</a>(const path& p, uintmax_t new_size, system::error_code& ec);</pre>
<blockquote>
Postconditions: <code>file_size() == new_size</code>.
Throws: As specified in
@@ -2233,7 +2224,7 @@
 truncate()</a></code>.
</blockquote>
<pre>space_info <a name="space">space</a>(const path& p);
-space_info <a name="space">space</a>(const path& p, system::error_code& ec);</pre>
+space_info <a name="space2">space</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Returns: An object of type <code>
 <a href="#space_info">space_info</a></code>. The value of the <code>space_info</code> object is determined as if by
@@ -2268,7 +2259,7 @@
 cause an exception to be
thrown. -- end note] 
 </blockquote>
-<pre>file_status <a name="status">status</a>(const path& p, system::error_code& ec);</pre>
+<pre>file_status <a name="status2">status</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Effects: 
 <blockquote>
@@ -2369,7 +2360,7 @@
 Throws: Nothing.
</blockquote>
<pre>file_status <a name="symlink_status">symlink_status</a>(const path& p);
-file_status <a name="symlink_status">symlink_status</a>(const path& p, system::error_code& ec);</pre>
+file_status <a name="symlink_status2">symlink_status</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Effects:  Same as status(), above,
 except that the attributes
@@ -2389,7 +2380,7 @@
nothing.
</blockquote>
<pre>path <a name="system_complete">system_complete</a>(const path& p);
-path <a name="system_complete">system_complete</a>(const path& p, system::error_code& ec);</pre>
+path <a name="system_complete2">system_complete</a>(const path& p, system::error_code& ec);</pre>
<blockquote>
 Effects: Composes an absolute path from <code>p</code>, using the
 same rules used by the operating system to resolve a path passed as the
@@ -2508,8 +2499,7 @@
techniques to avoid breaking existing code in other environments, particularly
on operating systems allowing slashes in filenames.
[Note: The
-"do-the-right-thing" rule from <a href="#Requirements-on-implementations">
-Requirements on implementations</a> does apply to header <code><fstream></code>.
+"do-the-right-thing" rule in the conformance section does apply to header <code><fstream></code>.
The overloads
below are specified as additions rather than replacements for existing
functions. This preserves existing code (perhaps
@@ -2526,14 +2516,14 @@
sentence:
<blockquote>
It then opens a file, if possible,
-whose name is the NTBS s (Ã¢â‚¬Å“as ifÃ¢â‚¬Â by calling <code>std::fopen(s ,modstr
+whose name is the NTBS s (as if by calling <code>std::fopen(s ,modstr
))</code>.
</blockquote>
with:
<blockquote>
It then opens, if possible, the file
that
-<code>p</code> or <code>path(s)</code> resolves to, Ã¢â‚¬Å“as ifÃ¢â‚¬Â by calling <code>std::fopen()</code> with a
+<code>p</code> or <code>path(s)</code> resolves to, as if by calling <code>std::fopen()</code> with a
second argument of modstr.
</blockquote>
In 27.8.1.5 Class template
@@ -3132,8 +3122,7 @@
implementations</h2>
The change in semantics to functions
taking <code>const char*</code> arguments can break existing code, but only on
-operating systems where implementations don't
-implicitly accept native format pathnames or
+operating systems where implementations don't implicitly accept native format pathnames or
operating systems that allow slashes in filenames. Thus on POSIX,
Windows, and OpenVMS, for example, there is no problem if the
implementation follows encouraged behavior.
@@ -3196,11 +3185,11 @@
 </tr>
</table>
<hr>
-Â© Copyright Beman Dawes, 2002, 2006, 2007, 2009
+© Copyright Beman Dawes, 2002, 2006, 2007, 2009
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
-17 January 2010
+18 January 2010

</body>

Next message: bdawes_at_[hidden]: "[Boost-commit] svn:boost r59127 - website/public_html/beta/community"
Previous message: strasser_at_[hidden]: "[Boost-commit] svn:boost r59125 - sandbox/transaction/dev"

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