Bug while updating MessageTally

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
6 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug while updating MessageTally

Nicolas Cellier
MessageTally close seems to be using a deprecated message.
If the deprecated warnings preference is enabled, then there is a
fatal Error recursion...

Nicolas

Reply | Threaded
Open this post in threaded view
|

Re: Bug while updating MessageTally

Levente Uzonyi-2
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
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Bug while updating MessageTally

Nicolas Cellier
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 :)

Nicolas

2010/2/23 Levente Uzonyi <[hidden email]>:

> 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
>>
>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Bug while updating MessageTally

Levente Uzonyi-2
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 <[hidden email]>:
>> 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
>>>
>>>
>>
>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Bug while updating MessageTally

Levente Uzonyi-2
In reply to this post by Nicolas Cellier
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

Which method of Debugger sends MessageTally >> #close? Is it Debugger >>
#process:controller:context:?


Levente

>
> I solved it by disabling deprecation warnings first.
>
> Now, I can still see a few local sends of #close to be fixed :)
>
> Nicolas
>
> 2010/2/23 Levente Uzonyi <[hidden email]>:
>> 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
>>>
>>>
>>
>>
>
>

Reply | Threaded
Open this post in threaded view
|

Re: Bug while updating MessageTally

Nicolas Cellier
2010/2/24 Levente Uzonyi <[hidden email]>:

> 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
>
> Which method of Debugger sends MessageTally >> #close? Is it Debugger >>
> #process:controller:context:?
>
>
> Levente
>

Can't reproduce now, and I did not keep the image.
Maybe the last Tools version was not installed yet...
Nicolas

>>
>> I solved it by disabling deprecation warnings first.
>>
>> Now, I can still see a few local sends of #close to be fixed :)
>>
>> Nicolas
>>
>> 2010/2/23 Levente Uzonyi <[hidden email]>:
>>>
>>> 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
>>>>
>>>>
>>>
>>>
>>
>>
>
>