On Jan 14, 2011, at 11:24 AM, Denis Kudriashov wrote:
Sorry,
I meen DateAndTime now millisecond and DateAndTime now nanoSecond.
As I write in last mail. I found cuis fix of this in Pharo issues
where? Denis please provide more information else we all have to spend more time to answer and decide the next action. Stef
2011/1/14 Adrian Lienhard <adi@netstyle.ch> Hi Denis,
There's no method milliseconds (at least in my Pharo 1.1.1 image). Can you be more specific?
I assume you want to get the milli seconds of a timestamp, rather than the millisecond clock (DateAndTime millisecondClockValue).
When you create a new timestamp (TimeStamp now) the milli/nano seconds are indeed 0. The reason is that the timestamp is initialized from "Time totalSeconds".
So I consider this not as a bug but something that could be improved.
Cheers, Adrian
BTW, I remember having seen a fix on Mantis (= Squeak bug tracker) which asserts that TimeStamp now < TimeStamp now.
On Jan 14, 2011, at 10:20 , Denis Kudriashov wrote:
Hello.
How I can get current time milliseconds parameter?
I try DateAndTime millisecond. But it always zero. And DateAndTime nanoSecond is always zero too.
Is it bug?
I use Pharo1.1