cheers -ben

On Thu, Dec 8, 2016 at 5:59 PM, phil@highoctane.be <phil@highoctane.be> wrote:
> What if the method is on class side?

Good point. Thus...
'class-side of AClass did not understand #message sent to it (MNU��AClass-class>>#message)'

>
> Phil
>
> On Thu, Dec 8, 2016 at 7:35 AM, Sven Van Caekenberghe <sven@stfx.eu> wrote:
>>
>>
>> > On 8 Dec 2016, at 00:42, Ben Coman <btc@openinworld.com> wrote:
>> >
>> > On Thu, Dec 8, 2016 at 5:54 AM, Denis Kudriashov <dionisiydk@gmail.com>
>> > wrote:
>> >> Done: ��19441.
>> >>
>> >> I also change nil case to "message was send to nil" (instead of
>> >> "receiver of
>> >> message is nil"). You can correct it as you wish :)
>> >
>> > send==>sent
>> >
>> >>
>> >> 2016-12-07 21:44 GMT+01:00 stepharong <stepharong@free.fr>:
>> >>>
>> >>> Hi guys
>> >>>
>> >>> As I exposed newbies to our wonderfull debugger I think that we should
>> >>> change
>> >>>
>> >>> MessageNotUnderstood: Class>>#message
>> >>>
>> >>> into
>> >>>
>> >>> an instance of Class did not understand message
>> >
>> > Perhaps(?) a short form can be put in brackets?
>> > ==> an instance of Class did not understand #message sent to it (MNU
>> > Class>>#message)
>>
>> +1
>>
>> > cheers -ben
>> >
>> >>>
>> >>> To me this simple change would have a HUGE impact on making the
>> >>> debugger
>> >>> first contact a lot more friendly.
>>
>>
>