Issue 3816 in pharo: Time millisecondClockValue wraps around way too quickly

Status: New
Owner: ----

New issue 3816 by [hidden email]: Time millisecondClockValue wraps  
around way too quickly
http://code.google.com/p/pharo/issues/detail?id=3816

Time millisecondClockValue seems to wrap around way too soon.

It is used for example by Seaside to track uptime.

I submitted a workaround to Seaside 3.0,  
http://code.google.com/p/seaside/issues/detail?id=596,  
http://www.squeaksource.com/Seaside30/Seaside-Pharo-Tools-Web-pmm.29.mcz.

This is a primitive (135) and I haven't looked at it, but I guess it is a  
32-bit integer, maybe a 64-bit integer would be better ?

Sven