Does that mean that it is wrong in 1.1? BTW, such changes/bugs are important to know for people who run critical applications. So we should carefully documented these. Just one example that bite us: (Duration seconds: 0.5) asSeconds --> 0, whereas in Squeak 3.9 it returned 0.5. Changes like these can break code in subtle ways...
Cheers, Adrian On Aug 13, 2010, at 22:35 , Mariano Martinez Peck wrote: > On Fri, Aug 13, 2010 at 10:32 PM, Stéphane Ducasse < > [email protected]> wrote: > >> In pharo 1.2 it should be local aware I integrated a fix of sean that made >> it start by default in localtime. >> >> > mmmm that's seem to be the problem :) > > If I know run the same in Pharo 1.2: > > Date today start -> 2010-08-13T00:00:00+02:00 > > the same as 1.0.... > > thanks :) > > mariano > > >> Stef >> >>> Hi folks. >>> >>> In Pharo 1.0 I evaluate "Date today start" i get -> >> 2010-08-13T00:00:00+02:00 >>> >>> and in Pharo 1.1 "Date today start -> 2010-08-13T00:00:00+00:00 >>> >>> so.... in 1.0 I have at the end a +02:00 and in Pharo 1.1 I have >> +00:00 >>> >>> which one is correct? are we aware of this change? does someone know the >> issue number of this? >>> >>> thanks >>> >>> mariano >>> _______________________________________________ >>> 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 _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
