Re: [Boost-users] [BULK] Re: [BULK] [filesystem] function to determineavailable space

-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: Monday, September 12, 2005 2:20 PM To: boost-users@lists.boost.org Subject: [BULK] Re: [Boost-users] [BULK] [filesystem] function to determineavailable space Importance: Low

"Sohail Somani" wrote in message news:1C1EBEF8DBACDC439D038EA051674EC709C5D4@xbox.financialcad.com...

...

...

-----Original Message----- From: boost-users-bounces@lists.boost.org [mailto:boost-users-bounces@lists.boost.org] On Behalf Of Beman Dawes Sent: Monday, September 12, 2005 10:23 AM To: boost-users@lists.boost.org Subject: [BULK] [Boost-users] [filesystem] function to determine available space Importance: Low

I'm planning to add a filesystem function to determine available disk space. Perhaps something like:

struct space_status { boost::uintmax_t available; // free space available to user boost::uintmax_t total; // total space on volume };

space_status filesystem_space( const path & p );

Comments?

Standard unit of measure? Bytes? Megabytes? Gigabytes?

Bytes. Individual bytes still matter in some applications.

What about using a type that guarantees a certain amount instead of just "max" (which may vary)? Or equivalently, are we guaranteed that uintmax_t can hold, say one TB, on any platform that boost supports?