Well even simple functionality would be very useful:
1) The ability to set read/write/delete access to the
file/directory for other processes.
2) The ability to get an OS specific handle to the
file/directory from the Boost.Filesystem lib so that
you can then manipulate file permissions yourself.
For example, a method signature like
boost::file_handle get_filehandle() where
boost::file_handle is a typedef per OS. But that
would totally break encapsulation for all the iostream
libraries, right?
Elisha
--- Sebastian Redl
Calderon Hector wrote:
I doesn't have to support every operative system out there. Can it be done to support the major operative systems at least?
Still not easily. Windows and Unix have quite different permission systems: Windows uses access control lists, which support fine-grained control of who is able to access which files. Unix uses user/group/world permissions, which are far less fine-grained, with some *nices in some configurations supporting POSIX ACLs too. (For example, this is a compile flag that must be enabled for the file systems in the Linux kernel.)
Finding a common interface for even these two is therefore very difficult. I'm sure though that there would be interest in any ideas you might have.
Sebastian Redl _______________________________________________ Boost-users mailing list Boost-users@lists.boost.org