Smaller than milliseconds?

Dar Scott dsc at swcp.com
Thu Jul 10 18:04:00 EDT 2003


On Thursday, July 10, 2003, at 02:57 PM, miscdas at boxfrog.com wrote:

> try this:
> put the long ticks into tTicks
> wait 1 tick
> put(the long ticks - tTicks)
> on WINXP pro, the result is in microtick resolution
>
> But,
> put the long seconds into tSecs
> wait 1 second
> put(the long seconds - tSecs)
> gives only millisecond resolution

Hmmmm.  LONG ticks?  Hey, I just noticed there are LONG milliseconds!  
Wow!

For this handler (needs field "Report"):

on mouseUp
   put the long seconds into time1
   put the long seconds into time2
   put "the long seconds: " & time2 && "delta: " & (time2-time1) & LF 
into field "Report"
   put the ticks into time1
   put the ticks into time2
   put "the ticks: " & time2 && "delta: " & (time2-time1) & LF after 
field "Report"
   put the milliseconds into time1
   put the milliseconds into time2
   put "the milliseconds: " & time2 && "delta: " & (time2-time1) & LF 
after field "Report"
   put the long ticks into time1
   put the long ticks into time2
   put "the long ticks: " & time2 && "delta: " & (time2-time1) & LF 
after field "Report"
   put the long milliseconds into time1
   put the long milliseconds into time2
   put "the long milliseconds: " & time2 && "delta: " & (time2-time1) & 
LF after field "Report"
end mouseUp

On my OS X, I get this:

the long seconds: 1057873624.51924 delta: 0.000009
the ticks: 63472417471 delta: 0
the milliseconds: 1057873624527 delta: 0
the long ticks: 63472417471.80954 delta: 0.000778
the long milliseconds: 1057873624533.140991 delta: 0.014038

I forgot how many digits we get with double floating point.  Between 14 
and 15?  This might limit how small of a time we can measure.

What do you folks get?

Dar Scott




More information about the metacard mailing list