In VA Smalltalk "Time millisecondClockValue" answers an integer number of
milliseconds from the time the OS was booted.  I know this is the case
under Windows and I think it is the same under Linux.

It should be continuous and ever increasing.  It is a four byte integer and
as such will wrap around to 0 after about 49 days.  I have read where it
may be adjusted for a change in daylight savings time but I don't think
that is the case.  It also doesn't seem to be effected by a change in the
time of day clock.

Lou

On Mon, 15 Feb 2016 10:18:01 -0800, Bert Freudenberg <bert at freudenbergs.de>
wrote:

>
>> On 15.02.2016, at 15:58, commits at source.squeak.org wrote:
>> 
>> 
>> Fixes a regression in Morphic's inter-cycle delay. Hacking during the switch from DST to normal time forced the user to wait one hour. Opening images from different time zones did also show this bug.
>
>What?!
>
>Time millisecondClockValue is supposed to be continuous. I’ll have to admit I didn’t follow the previous discussion too closely, but syncing millisecondClockValue to the wall clock seems like a very bad idea.
>
>- Bert -
-- 
Louis LaBrunda
Keystone Software Corp.
SkypeMe callto://PhotonDemon