On 09/22/2011 10:03 AM, Paolo Bonzini wrote: > On 09/22/2011 12:55 AM, Holger Hans Peter Freyther wrote: >> Delay.TimeoutSem signal > > Good, thanks. > >> probably combined with restoring the uptime could be quite nice. My current >> 'timer' code is using wall-clock time... i plan to update it to a monotonic >> tick, it would be nice if Time millisecondsClockValue would be that. > > millisecondsClockValue is monotonic, just not across image saves.
Okay, how to move forward then: a) we keep track of alarms and we expire them on image resume? this will probably require modifications to the image format? We use addDependent on Time to save/restore the millisecondsClockValue? b) We just let each Delay expire after a image restoration? E.g. by a resume handler that sets the expected millisecondsClockValue to 0 and then calls the Delay.Timeout... signal handler... different: Looking at the code, it appears that Process signal: atMilliseconds can only be used by one user on the VM? _______________________________________________ help-smalltalk mailing list [email protected] https://lists.gnu.org/mailman/listinfo/help-smalltalk
