Re: after ids

Alexandre Ferrieux <alexandre.ferrieux@xxxxxxxxx> wrote:
Would [clock alarm] make sense, rather than adding a new [at] command?
Its placement as a sub-command of [clock] also points directly at the
fact that this command is based on wall-clock time, rather than elapsed
time.

An alias is always possible of course, but keep in mind that this wall-
clock semantics has been attached to [after] since the beginning,

But always in contradiction to documentation:
" after ms
" Ms must be an integer giving a time in milliseconds.
" The command sleeps for ms milliseconds and then returns.
" ...
" after ms ?script script script ...?
" ..., but it arranges for a Tcl command to be executed
" ms milliseconds later as an event handler.

There is no mention that the future wallclock time is calculated
and then awaited but only of a timespan that's supposed to pass.

it must stay that way. So you also should invent a nice name for the
new, truly relative timers...
I disagree.

PS: The whole issue is only relevant if the underlying system
clock has a tendency to run unsteadily, which was probably
the reason for not caring back when "after" was designed.

.

Relevant Pages

  • Re: fooled by shifting date
    ... In this form the command returns immediately, but it arranges for a Tcl command to be executed ms milliseconds later as an event handler. ... There are at least two simple solutions to this: Put your clock in UTC and don't screw with it, or fix the code to work the way you want. ...
    (comp.lang.tcl)
  • Re: 2D graphics & speed quest
    ... Besides, I really didn't expect to see any individual updates for PolyLine to draw just 1000 lines, because I expected it to be completed too quickly to visibly identify the different stages of the drawing, but I could definitely see them plain as day, whereas I couldn't see any at all for the LineTo drawing. ... Obviously I was seeing them simply because PolyLine was taking an unexpected amount of time, about 14,000 milliseconds on my machine for the 100 iterations of the NumDraw loop, or about 140 milliseconds for the first loop. ... However, I just happened to be running your code with a Command Button on the Form, and it turns out that the "hole in the clipping region" was slowing things down by a massive amount, certainly much more than I would have expected. ...
    (microsoft.public.vb.general.discussion)
  • TIP #173: Internationalisation and Refactoring of the clock Command
    ... The [clock] command provides Tcl's fundamental facilities for computing ... {locale era, locale year, month, day of month}: ... If the given format does not include a time zone, ...
    (comp.lang.tcl)
  • 2.6.22-rc regression: smartctl does not work with SATA disk
    ... disk /dev/sdb is a SATA disk. ... The command does work still with a real SCSI ... ATA Standard is: Exact ATA specification draft version not indicated ...
    (Linux-Kernel)
  • Re: Trouble with some simple programming
    ... When the user clicks on another command button, ... > Dim CurConn As New ADODB.Connection ... interface consists basically of a "time clock" form with a continuous ... Private Sub cmdStart_Click ...
    (microsoft.public.access.modulesdaovba)