So Camillo, can we just print the name of the collection (instead of all of it and get the loop) in the description of KeyNotFound?

thanks

On Fri, May 20, 2011 at 9:27 AM, St�phane Ducasse <stephane.ducasse@inria.fr> wrote:
I would like to have tests covering that!

On May 20, 2011, at 12:34 AM, Camillo Bruni wrote:

>
> On 2011-05-20, at 00:03, Mariano Martinez Peck wrote:
>
>> On Thu, May 19, 2011 at 11:55 PM, Camillo Bruni <camillo.bruni@inria.fr>wrote:
>>
>>> IMO this shouldn't change a thing, since KeyNotFound inherits from Error...
>>> having a look at it
>>>
>>> yes i know :(
>> but in pharo 1.2 it works. That's why �I thought it could be related to
>> that.
>
> ok, the bug seems to be related to catching the signaller, dunno why, but commenting out the section on Exception >> signal seems to solve the issue.
>
> I will have a look at it tomorrow.
>
> camillo
>
>>> On 2011-05-19, at 23:45, Mariano Martinez Peck wrote:
>>>> So...it seems Pharo1.3 change Dictionary to throw KeyNotFound instead of
>>> Error.
>>>> Now, my image freezes with a loop. I would appreciate some help. I
>>> couldn't really analyzed the problem.
>>>> Fileine both FLPerson.st and ATest and run the test testDictionaryRehash.
>>>> In such test, a the end there is a
>>>>
>>>> � self shouldnt: [aDictionary at: newPerson1] raise: KeyNotFound.
>>>>
>>>>
>>>> which raises the debugger pre-popup. if I try to click on the popup... ->
>>> loop/freeze.
>>>> You can interrupt it and see more or less what is happening.
>>>>
>>>> Camillo, can you take a look?
>>>
>>
>>
>>
>> --
>> Mariano
>> http://marianopeck.wordpress.com
>
>




--
Mariano
http://marianopeck.wordpress.com