[squeak-dev] Bug while updating MessageTally
Levente Uzonyi
leves at elte.hu
Tue Feb 23 23:12:56 UTC 2010
On Tue, 23 Feb 2010, Nicolas Cellier wrote:
> Don't know what happened...
> This seems to have been triggered by my own bug (sending
> peekSignIsMinus to sourceStream instead of self).
> -> Debugger -> MessageTally close -> deprecation exception
>
> I solved it by disabling deprecation warnings first.
>
> Now, I can still see a few local sends of #close to be fixed :)
Oops. That's my fault, I thought I removed all #close sends from
MessageTally.
Levente
>
> Nicolas
>
> 2010/2/23 Levente Uzonyi <leves at elte.hu>:
>> On Tue, 23 Feb 2010, Nicolas Cellier wrote:
>>
>>> MessageTally close seems to be using a deprecated message.
>>
>> MessageTally >> #close is the deprecated message.
>>
>>> If the deprecated warnings preference is enabled, then there is a
>>> fatal Error recursion...
>>
>> That can only happen if you loaded System-ul.258 but not Tools-ul.190 which
>> is pretty unlikely.
>>
>>
>> Levente
>>
>>>
>>> Nicolas
>>>
>>>
>>
>>
>
>
More information about the Squeak-dev
mailing list
|