<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.6000.16525" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff
size=2></FONT> </DIV>
<DIV></DIV>
<DIV><SPAN class=781434722-18092007><FONT face=Arial color=#0000ff
size=2> > </FONT></SPAN>Array is a class, not a message. This is
/not/ elegant and simply doesn't make sense. This is my last comment on this
approach.<SPAN class=781434722-18092007><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN></DIV>
<DIV><SPAN class=781434722-18092007></SPAN> </DIV>
<DIV><SPAN class=781434722-18092007><FONT face=Arial color=#0000ff size=2>That's
not strictly correct. In the given example it is a message: you are simply
asking the given namespace to answer the named class, and the only confusing
thing about it is the message is capitalized. </FONT></SPAN><SPAN
class=781434722-18092007><FONT face=Arial color=#0000ff size=2> What if it were
written as "Kernel array new:4"? </FONT></SPAN></DIV>
<DIV><SPAN class=781434722-18092007></SPAN><SPAN class=781434722-18092007><FONT
face=Arial color=#0000ff size=2>It is already possible to create a capitalized
message in Squeak, we just avoid it because it gets confusing. However in the
given context I simply applaud Dan's genius and I second that it is a simple and
elegant solution. For the more conservative approach I would have no problem
with a namespace creating a non-capitalized accessor message for the given class
but that could cause other
confusions. </FONT></SPAN></DIV>
<DIV><SPAN class=781434722-18092007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=781434722-18092007><FONT face=Arial color=#0000ff
size=2>Tansel</FONT> </SPAN></DIV>
<DIV><SPAN class=781434722-18092007><FONT face=Arial color=#0000ff
size=2></FONT></SPAN><BR><SPAN class=781434722-18092007><FONT face=Arial
color=#0000ff size=2> <FONT face="Times New Roman" color=#000000
size=3>> </FONT> </FONT></SPAN>+10000 for:<BR><SPAN
class=781434722-18092007><FONT face=Arial color=#0000ff size=2> <FONT
face="Times New Roman" color=#000000 size=3>> </FONT> </FONT></SPAN>self
add: (Kernel Array new: 4).<BR><SPAN class=781434722-18092007><FONT face=Arial
color=#0000ff size=2> <FONT face="Times New Roman" color=#000000
size=3>> </FONT> </FONT></SPAN>This mechanism preseves the elegant
foundation of Smalltalk: 'Everyting is an Object, which receives a messages and
returns an object'.<BR><SPAN class=781434722-18092007><FONT face=Arial
color=#0000ff size=2> <FONT face="Times New Roman" color=#000000
size=3>> </FONT> </FONT></SPAN>In this (Dan's ?) solution, the
implementation is late bound and can use the same lookup algorithm as used for
messages<SPAN class=781434722-18092007><FONT face=Arial color=#0000ff
size=2> </FONT></SPAN>. <SPAN
class=781434722-18092007> </SPAN><BR><SPAN class=781434722-18092007><FONT
face=Arial color=#0000ff size=2> <FONT face="Times New Roman" color=#000000
size=3>> </FONT> </FONT></SPAN>The other solutions lack this
elegance.<BR></DIV></BODY></HTML>