On Wed, Jan 25, 2006 at 09:10:50PM +0000, Alberto Simões wrote: > 2) What it might be. > > My first idea is to join both PMCs, and create a FileSystem PMC. The > main problem is its name. After looking to Python discussion, and > thinking a little on the PIR syntax, I would call it Path.
> 3) Implementation > > Some discussion have taken place before regarding copy and rename > implementation. I think we can subclass this PMC for specific OSes, and > specific FileSystems if needed. Is your implementation going to cope with one OS having several different types of file systems mounted, that might have different specific behaviours? I know that HFS+, ufs and ext3 all have various forms of flags/extended attributes, and in turn I'd assume that a FileSystem PMC would have some way of accessing them. So I'd assume that parrot has to cope gracefully with this, and allow full access, although maybe not as far as automatic detection. Nicholas Clark
