mirror of
https://github.com/boostorg/filesystem.git
synced 2026-01-31 20:22:07 +00:00
33 lines
1.3 KiB
HTML
33 lines
1.3 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.<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>Get opinions on default, Boost, and other error checks. POSIX?
|
|
Windows? ISO 6990?<br>
|
|
</li>
|
|
<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.</li>
|
|
</ul>
|
|
<hr>
|
|
<p>© Copyright Beman Dawes, 2002</p>
|
|
<p>Revised
|
|
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->30 July, 2002<!--webbot bot="Timestamp" endspan i-checksum="21079" --></p> |