<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
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.<br>
<br>
Cheers,<br>
Josh<br>
<br>
<br>
<br>
Igor Stasenko wrote:
<blockquote
cite="mid:4a5f5f320811111537p6391badcve69c8f4b6fbf1f29@mail.gmail.com"
type="cite">
<pre wrap="">2008/11/12 Keith Hodges <a class="moz-txt-link-rfc2396E" href="mailto:keith_hodges@yahoo.co.uk"><keith_hodges@yahoo.co.uk></a>:
</pre>
<blockquote type="cite">
<pre wrap="">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?
</pre>
</blockquote>
<pre wrap=""><!---->both? :)
</pre>
<blockquote type="cite">
<pre wrap="">Keith
</pre>
</blockquote>
<pre wrap=""><!---->
</pre>
</blockquote>
<br>
</body>
</html>