Re: Recommended way of specifying file paths?

[David Sugar]

File was designed originally for a very different purpose than fstream; it was 
meant for portable paged (block oriented) i/o, such as might be used in 
creating data stores in database systems, or in record oriented operations.  
It exists in several flavors representing ideas for block i/o in regards to 
threading and could be an interesting foundation for a threaded database 
engine.

On Friday 31 January 2003 20:31, Ari Johnson wrote:
> Is there a recommended cross-platform way to specify paths to files that
> works on both Windows and *nix, using CommonC++?  Also, would the
> CommonC++ File interface be any more or less portable to use than fstream
> and friends?
>
> Ari Johnson
>
>
>
>
> _______________________________________________
> Bug-commoncpp mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/bug-commoncpp