"Thomas Matelich"
On 6/22/05, Beman Dawes
wrote: "Thomas Matelich"
wrote in message news:3944d45805062113231fa767ff@mail.gmail.com... Probably a dumb question, but why did you use
and statfs() instead of the POSIX and statvfs()? Were they not present on some of the target systems? I would like to include the functionality in Boost.Filesystem, but am concerned because POSIX lists it as optional.
I started with our legacy HP implementation as a reference and didn't need to change it for linux, so I didn't even notice that there was a different header. :-)
Understood. Does the legacy HP implementation also supply
I'd be fairly surprised if a platform supported by Filesystem didn't have a way to determine disk space. Well, I guess not all that surprised. Murphy's always waitin'.
Yep. But that isn't necessarily a showstopper. 1.34 will add a function to create hard links, and just document the fact that it will always fail on some file systems. To me the key platforms are POSIX/Windows/Linux/Solaris/MacOS/HPux/AIX. If we get uniform behavior across those platforms, it is OK if a function can't succeed on more obscure platforms. --Beman