I _think_ we would almost have to include both for migration. FileDirectory is awful. +1 on the idea of killing it. -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Adrian Lienhard Sent: Thursday, November 19, 2009 9:32 AM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Is there a small and effective File library around? +1 Would we include this new Filesystem besides the old FileDirectory implementation to simplify migration of external code? Adrian On Nov 19, 2009, at 14:41 , Marcus Denker wrote:
On Nov 19, 2009, at 2:38 PM, Lukas Renggli wrote:
I am using Filesystem from http://source.wiresong.ca/mc/ from Colin. As far as I know an official release is imminent.
It is an amazing library, well documented and well tested with almost 400 unit tests (they all pass in Pharo). It supports uniform access to the filesystem, zip archives and in-memory filesystems (for tests). It supports different enumeration strategies and platform specific locations (such as home-directory, desktop, etc).
Filesystem is built on the existing primitives, but does not depend on FileDirectory and FileStream. I already mentioned this library several times in the list and suggested to include it with Pharo core and kill FileDirectory.
+ 1000
Marcus
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project