Hello folks<div><br></div><div>I was wondering why does Smalltlak prefer the printOn: aStream method over the printString method.</div><div><br></div><div>As I work with Java and C# all the time, I&#39;m used to define a printString like method where you return a string representing the object,</div>

<div>and, today, having to do the same in smalltlak I��unconsciously��redefined the printString method. As soon as I realize that my collections were using printOn: instead of my redefined printSrting method for printing their contents, I wondered:</div>

<div><br></div><div>Why was this decision taken? I mean, every other language seems more simple (from the end user point of view, as it does not��require��the user to��understand��streams at all),��In the other hand, printOn: seems more versatile.</div>

<div><br></div><div>Pointless question, I know, but I&#39;m quite curious and I cannot seem to find anything about this, and I though that you guys may know.</div><div><br></div><div>Cheers</div><div>-- <br>Alan Rodas Bonjour<br>

<br>
</div>