filesystem/doc/do-list.htm

<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>Windows: Some files seem to be poisoned to the point where you can't even 
  do is_directory() on them without an access error. For example,&nbsp; pagefile.sys. Should directory_iterator ignore these files?<br>
&nbsp;</li>
  <li>Windows: //share style paths need more analysis and test cases for system_complete() 
  and complete(). Also, path_test cases at line 410 need review, correction.<br>
&nbsp;</li>
  <li>Add a path::swap member function guaranteed not to throw. (Geurt Vos).<br>
&nbsp;</li>
  <li>Windows: What happens when a directory_itorator encounters a 
  wide-character filename? Write a test case.</li>
</ul>
<ul>
  <li>Add &quot;.&quot; current directory to generic path? Add test cases one 
  way or the other. Change simple_ls accordingly.<br>
&nbsp;</li>
  <li>Ask for help porting to other operating systems, such as the Mac, etc.</li>
</ul>
<ul>
  <li>Finish the probe program, and ask Boost people to run it on various O/S's.<br>
&nbsp;</li>
  <li>Finish portability guide and checking functions. Get opinions on default, Boost, and other error checks.&nbsp; POSIX?&nbsp; 
  Windows? Mac?&nbsp; ISO 6990? Document the checking functions.<br>
&nbsp;</li>
  <li>Operations_test line 171 - why only check iterator tag? Why not 
  Assignable, etc?<br>
&nbsp;</li>
  <li>The wrapped fstream functions which return the type of the stream (*this) 
  would have to be overridden to get the wrapped type (boost::filesystem::ifstream 
  rather than std::ifstream, for example). But does it matter? Does anyone care? 
  Will any programs fail?<br>
&nbsp;</li>
</ul>
<hr>
<p>© Copyright Beman Dawes, 2002</p>
<p>Revised
<!--webbot bot="Timestamp" S-Type="EDITED" S-Format="%d %B, %Y" startspan -->23 March, 2003<!--webbot bot="Timestamp" endspan i-checksum="28836" --></p>