mirror of
https://github.com/boostorg/filesystem.git
synced 2025-05-12 05:31:49 +00:00
45 lines
1.8 KiB
HTML
45 lines
1.8 KiB
HTML
<title>Boost Filesystem Do-list</title>
|
|
<h1>
|
|
<img border="0" src="../../../c++boost.gif" align="center" width="277" height="86">Filesystem
|
|
Do-list</h1>
|
|
<ul>
|
|
<li>Finish the probe program, and ask Boost people to run it on various O/S's.<br>
|
|
</li>
|
|
<li>Finish portability guide and checking functions. Get opinions on default, Boost, and other error checks. POSIX?
|
|
Windows? Mac? ISO 6990?<br>
|
|
</li>
|
|
<li>Cyclic paths:</li>
|
|
</ul>
|
|
<blockquote>
|
|
<ul>
|
|
<li>General requirements.</li>
|
|
<li>Add cycle-breaking code if needed.</li>
|
|
<li>Add test case to make sure functions like <i>remove_all</i> don't loop.</li>
|
|
</ul>
|
|
</blockquote>
|
|
<ul>
|
|
<li>As a lexical concept, parent-directory is portable unless it escapes to
|
|
the operating system. But do all operating recognize such a concept in a path?
|
|
I doubt it. Maybe there should be a checking function that verifies that
|
|
generic_path() contains no <code>".."</code>.<br>
|
|
</li>
|
|
<li>Once the review is complete, ask for help porting to the Mac, etc.<br>
|
|
</li>
|
|
<li>From John Maddock:</li>
|
|
</ul>
|
|
<blockquote>
|
|
<pre>>All the functions generic_path, file_path, directory_path, leaf, and
|
|
>branch,
|
|
>are under-documented IMO. I had to read the specs quite closely before I
|
|
>could figure out which did what. Adding examples to each would probably be
|
|
>a help, or maybe a "description" section that provides a less terse
|
|
>description than the standardese.</pre>
|
|
</blockquote>
|
|
<ul>
|
|
<li>Change remove() to return a bool, now that the file doesn't have to
|
|
exist.. (Keith Burton)</li>
|
|
</ul>
|
|
<hr>
|
|
<p>© Copyright Beman Dawes, 2002</p>
|
|
<p>Revised
|
|
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->22 September, 2002<!--webbot bot="Timestamp" endspan i-checksum="39335" --></p> |