Re: [TCLCORE] To the best of my recollection regarding TIP#302

[Harald O. <har...@el...>]

Am 05.05.2025 um 20:45 schrieb Christian Werner:
> Hello all,
> 
> some points to discuss:
> 
> * the clock domain should be switched from wall clock to a monotonic 
> clock source in POSIX speak
> * this should ideally not have an impact on time computations in Tcl core
> * however, POSIX monotonic clock must be used in both clock_gettime() 
> and condition variables
> * maybe it's a good idea to detect availability of monotonic clock and 
> fall back to wall clock if not available
> * the time bound on slave interp evaluations is unfortunately in wall 
> time which is IMO a failure in design
> * what about virtual time, can this be ditched entirely, there ain't no 
> test cases and no examples
> * the "after -at" form is a special case to allow for cron like 
> requirements, is this ever a use case?
> * what is the resolution of "after -at", when it's like cron one second 
> seems enough
> * for symmetry another "after -mono" can be imagined which is like 
> "after -at" but in the monotonic clock domain
> * the resolution of "after -mono" should be near the tick rates of 
> contemporary OSes (e.g. milliseconds)
> 
> Best regards,
> Christian
Christian, Sergey,
thank you for your valuable contributions.
We need that!
It is an absolute requirement for an integration system to work.

Yesterday, in the meeting, there was a strong objection to:
- change current after in using the wall clock
- not use a command switch, but a new command for the new monolitic 
after, as this is seen as the future.

The way is not so important. Important is to get it. But sematics is 
always good for discussions ;-).

Christian, I am probably blind. Where is your "after -at" patch ?

Sergey, would it possible to extract the monolitic clock part of your 
big code contributions ?

Thanks for all, this discussion rocks! Lets get it fly!
Harald