Re: [clock] behaves just slow (Re: [clock scan] behaves inconsistently in Tcl8.5
Available news archives: comp.lang.tcl - comp.lang.python - comp.security.firewalls - sci.crypt - comp.lang.php - comp.lang.javascript
Google
 
Web news.hping.org


comp.lang.tcl archive

Re: [clock] behaves just slow (Re: [clock scan] behaves inconsistently in Tcl8.5

From: Donal K. Fellows <donal.k.fellows@manchester.ac.uk>
Date: Wed Sep 07 2005 - 14:54:35 CEST

Andreas Leitgeb wrote:
> Checking for the string "now" inside [clock format ...]
> and [clock add ...] does *not* infer shimmering, if it
> is done correctly: if an integer-representation exists,
> then the "now"-check can safely be skipped. otherwise
> if a string-rep exists (or has to be obtained, anyway,
> as an interims-result), the "now"-check should be really
> cheap.

In 8.5, most of the [clock] subcommands are just procedures. This
includes [clock format], [clock scan] and [clock add] (but not [clock
seconds] or [clock clicks], for fairly obvious reasons). Avoiding
shimmering in such circumstances is trickier.

Donal.
Received on Thu Sep 29 14:35:52 2005