Ok, I got it working by splitting the change into 3 packages that need to be integrated separately. All chronology tests pass.
Would be nice if you consider integrating it. Norbert Am 26.09.2011 um 20:30 schrieb Stéphane Ducasse: > tx for the information > > On Sep 26, 2011, at 6:50 PM, Norbert Hartl wrote: > >> >> Am 26.09.2011 um 18:19 schrieb Stéphane Ducasse: >> >>> sure it will >> >> Now I see why it wasn't integrated. The fix is not that easy as it is in the >> bug entry. >> >>> Now did you check the motivation? >> >> Of the issue? Of course, to get time information that contains milliseconds >> and not only seconds. >> >>> Was it good? >> >> I think yes. The milliSecondClock is nothing reliable. You need to fiddle >> with it to get a real millisecond value. >> >>> Worth to get it in? >> >> Yes, I need to be able to measure milliseconds. I could use milliSecondClock >> but I think it is good for pharo to integrate it into DateAndTime properly. >> >> Norbert >> >>> On Sep 26, 2011, at 5:24 PM, Norbert Hartl wrote: >>> >>>> >>>> Am 26.09.2011 um 16:40 schrieb Marcus Denker: >>>> >>>>> >>>>> On Sep 26, 2011, at 4:36 PM, Norbert Hartl wrote: >>>>> >>>>>> Does anybody know what happened to >>>>>> >>>>>> http://code.google.com/p/pharo/issues/detail?id=3236 >>>>>> >>>>>> In pharo-1.3 and pharo-1.4 they aren't in. Well, that matches the status >>>>>> of FixedWaitingToBePharoed. Last change by Marcus is from April 7th. >>>>>> >>>>> >>>>> Every issue not closed has yet to be done. >>>>> >>>>> So the anwer is: Nothing happend. >>>>> >>>> Ok, >>>> >>>> there was only a diff so I guess it was more manual work to have it >>>> integrated. I'm redoing the stuff on a fresh 1.4 image so it can be easily >>>> integrated. I hope this will help getting it in. >>>> >>>> Norbert >>>> >>>> >>>> >>> >>> >> >> > >
