Re: Time in milliseconds
Re: Time in milliseconds
- Subject: Re: Time in milliseconds
- From: "Dennis W. Manasco" <email@hidden>
- Date: Sun, 1 Aug 2004 02:26:57 -0500
At 8:01 am -0400 7/31/04, Paul Skinner wrote:
{...}
Just to nit pick over something that bothered me about the original
code, and should have no real effect on the result, shouldn't the
last line be:
(((t2 - t1) / (r+2)) as text) & "ms per call" ?
The outer two calls are marking the begin and end points of
the timeframe. The first call sets the start time, a loop runs, then
a call sets the end time. Only the second call occurs inside the
timed window. To remove that call It should have been...
(((t2 - t1) / (r+1)) as text) & "ms per call"
{... some other interesting stuff about timing calls and some further
results...}
Paul --
Thanks.
For the record, my nit pick wasn't meant to be snarky. I was just
scratching my head wondering if I had missed something obvious. Turns
out I had, just not exactly what I thought I might have: My sleep
deprived brain was firing too slow to notice that the first call
established the initial bound and was outside the loop, even while it
caught the final call as being within the loop.
In this case the whole thing was trivial, but it's just the kind of
oversight on my part that drives me crazy: It leads to bugs and
inaccuracies from places that I _know_ are right because I fixed
them....
Wasn't it Kin Hubbard who said something like:
"It ain't what people don't know that's the problem, it's what they
know that ain't so."
Best wishes,
-=-Dennis
_______________________________________________
applescript-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/applescript-users
Do not post admin requests to the list. They will be ignored.