On 20.09.2014, at 03:02, Esteban A. Maringolo <emaringolo@gmail.com> wrote:

> 2014-09-19 20:59 GMT-03:00 Eliot Miranda <eliot.miranda@gmail.com>:
>>
>>
>> On Fri, Sep 19, 2014 at 1:19 AM, Max Leske <maxleske@gmail.com> wrote:
>>>
>>> This issue was more of a discussion between Camillo and Sven. They never
>>> reached a conclusion, so please take a look. I���ve compiled the transcript
>>> below.
>>>
>>> The issue isn���t easy to solve and maybe we can just close it as ���not
>>> important���.
>>
>>
>> +1.�� But isn't the selector printString: broken?
>
>
> The selector sounds broken to me too.
>
> I always bring Dolphin to the discussion, but Dolphin streams had both
> #print:/#display:
>
> WriteStream>>#print: anObject
>�� �� anObject printOn: aStream.
>
> WriteStream>>#display: anObject
>�� �� anObject displayOn: aStream.
>
> But those are for printing/displaying the argument on the stream,
> which is not exactly the same as sending #asString and then then
> appending the result to receiver. So Eliot's #printAsString: seems to
> be the most intention revealing selector for such task.

Ok, so how about adding WriteStream>>printAsString:? Implementation:

printAsString: anObject
�� �� �� �� self nextPutAll: anObject asString

Cheers,
Max

>
> Regards!
>