<div dir="ltr">I feel very strongly that . as a statement separator *must* be followed with at least one whitespace character and that the ramar should reflect this. But I know some people disagree strongly. If I were designing a successor language to smalltalk I would add this to the syntax. The argument fort me is one of readability and flexibility. I don't see 1 foo.2 bar.3 baz as readable.<div>
1 foo.</div><div> 2 bar.</div><div> 3 baz</div><div>is much more readable. Further, being able to use . in literal symbols is nice. The Borning/Ingalls multiple inheritance system used this feature so that one could say e.g.</div>
<div> self SomeSuperclass.selector</div><div>to indicate one wanted to use the implementation inherited from SomeSuperclass, instead of using the potentially ambiguous super.</div><div><br></div><div>So by requiring the statement separator to be a period and one or more whitespace characters the ambiguity disappears, and .2 could be legal Smalltalk syntax.<br>
<br><div class="gmail_quote">On Sun, Aug 31, 2008 at 2:33 PM, Alejandro F. Reimondo <span dir="ltr"><<a href="mailto:aleReimondo@smalltalking.net">aleReimondo@smalltalking.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi!<div class="Ih2E3d"><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
{ 0.2.3.4.5.6 } printString '#(0.2 3.4 5.6)'<br>
</blockquote></blockquote>
<br></div>
Under my eyes, the problem is related with<br>
the non-smalltalk syntax of braces...<br>
The problem is a side effect of queueing<br>
sentences in a pseudo-array notation<br>
(remove the braces and the ambiguity<br>
vanishes).<br>
<br>
IMO, all said to non-st numeric notation is<br>
correct, and the same work (of remotion)<br>
must be done on {....} syntax.<br>
The same is applicable to ifNil:... and friends<br>
because it promote the idea (in newbies) that<br>
it is better to write faster...<br>
<br>
cheers,<br>
Ale.<br>
<br>
<br>
<br>
<br>
----- Original Message ----- From: "nicolas cellier" <<a href="mailto:ncellier@ifrance.com" target="_blank">ncellier@ifrance.com</a>><br>
To: <<a href="mailto:squeak-dev@lists.squeakfoundation.org" target="_blank">squeak-dev@lists.squeakfoundation.org</a>><br>
Sent: Sunday, August 31, 2008 4:12 PM<br>
Subject: [squeak-dev] Re: Number readFrom: can we remove some "accidental"features<div><div></div><div class="Wj3C7c"><br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Igor Stasenko a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
2008/8/31 Stéphane Rollandin <<a href="mailto:lecteur@zogotounga.net" target="_blank">lecteur@zogotounga.net</a>>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Igor Stasenko a écrit :<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
My guess it can stay, but only as separate helper method, which reads<br>
a numbers and expecting non-smalltalk syntax.<br>
</blockquote>
yes, useful for end-user input in numerical applications.<br>
we could spare them the .2 = 2 experience...<br>
<br>
</blockquote>
<br>
Btw, everyone is content with such ambigility?<br>
<br>
{ 0.2.3.4.5.6 } printString '#(0.2 3.4 5.6)'<br>
<br>
</blockquote>
<br>
Yes funny.<br>
Guess in which language you can evaluate<br>
<br>
-3r=3r-.-3r-=3r<br>
<br>
No, it is not /etc/printcap.<br>
That's why Stef (Ducasse) asked for cleanup I guess.<br>
<br>
<br>
<br>
</blockquote>
<br>
<br>
<br>
</div></div></blockquote></div><br></div></div>