From: Carl Daniel (cpdaniel_at_[hidden])
Date: 2002-01-28 09:49:49
From: "Daryle Walker" <darylew_at_[hidden]>
> UNIX systems have all the disks (and disk-like devices) arranged under a
> virtual unified hierarchy. So it's very easy to store UNIX paths as a
> string with '/' separators. However, other platforms aren't that simple.
> There are different separators, volume separators, and possibly unique types
> of data (e.g. versions). So the path objects shouldn't store the path as a
> single string that needs parsing, but as a list of intermediate directory
> names, the final object, and possibly the volume designator and other data.
Dont know if this has been noted already or not - but another variation from the basic path on Windows is that of named
streams within files. Named streams have been supported by NTFS since NT3.1, but they're not well known and rarely
They use the syntax path/filenname:streamname. Named streams were implemented in NTFS to support Mac files, but they're
useable by any program (they're not well supported by Explorer & the other WYSIWIG tools, however).
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk