On Tue, Nov 11, 2008 at 4:25 PM, Keith Hodges <keith_hodges at yahoo.co.uk> wrote:
> Now that the architecture for Rio is complete. Its time for a vote!
>
> Current usage....
>
> 'someDir/someFile' asRio   -> instance of Rio.
> 'someDir/newDir' asRio mkdir -> instance of Rio.
> 'someDir/file.zip' asRio zip -> instance of RioArchive.
>
> Could change to usage.....
>
> 'someDir/someFile' asFile.  -> instance of File.
>
> 'someDir/newDir' asDirectory -> instance of Directory.
>
> 'someDir/file.zip' asFile zip -> instance of FileArchive.
>
> I like the original #asRio, and I wonder if there are any other
> smalltalks which already use #asFile and #asDirectory, and classes File
> and Directory. Nevertheless I can see why people would prefer the latter.
>
> votes?

I think you should stick with #asRio.  Methods like #asFile should be
reserved for a portability layer.  Programs that use the portable
versions shouldn't care which file package they are using, while those
that use #asRio can depend on special features of Rio.

One of the nice things about using #asRio is that then application
programs do not have to know about the names of classes.  Perhaps File
and Directory should be RioFile and RioDirectory to avoid namespace
collisions.

-Ralph