[squeak-dev] Socket clock rollover issues

stephan at stack.nl stephan at stack.nl
Tue Apr 28 09:20:35 UTC 2009


Nicolas Cellier wrote:
> In a Pharo image, I see 112 senders of #millisecondClockValue and only
> 5 of #millisecondsSince:
> That let room for future rollover-proof improvments...

My Seaside-2.8-578 image has 156 and 4. That looks like improvement to me :)

It looks like all scrolling behavior in Morphs is influenced by this.

Stephan



More information about the Squeak-dev mailing list