I'm wary of the potential for namespace collisions with names such as
#asFile and #asDirectory.  What about #asRioFile and #asRioDirectory? 
If Rio were to become so wildly popular that it is adopted as the
default, #asFile and #asDirectory might make more sense.

Cheers,
Josh



Igor Stasenko wrote:
> 2008/11/12 Keith Hodges <keith_hodges at yahoo.co.uk>:
>   
>> 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?
>>
>>     
> both? :)
>
>   
>> Keith
>>
>>
>>
>>     
>
>
>
>   

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20081112/7204e8c5/attachment.htm