Yes but when I load the fix the bug is still there. Did you slice changes this behavior? or the slice is just about adding a test that fails?
> Yes, that's the bug, identified by Nicolas > > Alexandre > > > On 25 Dec 2009, at 10:49, Stéphane Ducasse wrote: > >> I tried to understand >>> >>> >>> >>> A very simple example to illustrate the bug: >>> >>> | x | >>> x := (1.0 timesTwoPower: 53). >>> (x to: x + 2) size. >>> x to: x+2 do: [:i | Transcript cr; show: i printString] >> >> it is normal that it still loops forever after loading the slice? >> >> Stef >> >> _______________________________________________ >> Pharo-project mailing list >> [email protected] >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > > > > > _______________________________________________ > Pharo-project mailing list > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
