Hi. I was who reported that issue. If you can see, on Dec 07, 2009 I commented: "
yes, true. I would attach the fix in both 1.0 and 1.1 " I cannot do any more. I put it as Milestone-1.0 and fixed. Hope someone may integrate this so that it can be included in the next dev image I will build. Cheers Mariano On Mon, Jan 18, 2010 at 10:18 AM, Stéphane Ducasse < [email protected]> wrote: > > On Jan 18, 2010, at 10:13 AM, George Herolyants wrote: > > > Hi all, > > > > I've just checked in the latest dev image (10.01.1). The bug > > http://code.google.com/p/pharo/issues/detail?id=945 is still there > > despite it was marked as 'closed' in the tracker. > > Btw, Squeak Trunk incorporated not nil check as a workaround. I also > > did it in my working image (as many other people, I think). > > Did you publish a slice? or is it in your cs? > isNil is a way to often turn around the problem. > > > > So why > > doesn't Pharo do the same at least until the right fix will be > > proposed? > > time. time time time time time time time time > Probably and knowledge sometimes. This system is also complex :) > > > > I bother you with it because I believe it prevents Pharo to gain new > > users (at least those who mostly uses Windows platform). > > Thanks george we will have a look! > > > > > > George > > > > _______________________________________________ > > 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 >
_______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
