Hi Esteban.

We have method #displayOn: but it has different purpose: argument is a kind
of canvas. So it is not related.

2018-04-10 17:28 GMT+02:00 Esteban A. Maringolo <emaring...@gmail.com>:

> Isn't #displayString implemented in terms of #displayOn: the same way
> #printString is implemented in terms of "printOn:"?
>
> And in the case of String #displayString should return the receiver (it
> is, self), so the following should be true.
>
> | s |
> s := 'Hello, ''Funny'' World'.
> s displayString = s. "true"
> s printString = s. "false"
>
> Regards,
>
>
> On 10/04/2018 12:21, Denis Kudriashov wrote:
> > Hi.
> >
> > According to the comment of #displayString it should be used as default
> > textual representation of objects in the UI:
> >
> >     "While printString is about to give a detailled information about an
> >     object, displayString is a message that should return a short
> >     string-based representation to be used by list and related UI
> >     frameworks. By default, simply return printString."
> >     "asString should not be implemented in Object, and kept for
> >     conversion between strings, symbols, text and characters."
> >
> > But String itself does not respect this message:
> >
> >     'some string' displayString " ==> '''someString''' "
> >
> >
> > Is it bug? Or is there any reason for this?
> >
> > Best regards,
> > Denis
>
> --
> Esteban A. Maringolo
>
>

Reply via email to