Menu

#1125 [clock scan ""] yields surprising results

obsolete: 8.3b1
closed-fixed
nobody
2
2001-04-04
2000-10-26
Anonymous
No

OriginalBugID: 4144 Bug
Version: 8.3b1
SubmitDate: '2000-02-08'
LastModified: '2000-02-10'
Severity: MED
Status: Released
Submitter: techsupp
ChangedBy: hobbs
OS: Windows NT
OSVersion: NT 4 patchlevel 5
Machine: beige. rather boring, really. I wish it were Mac G4 :-)
FixedDate: '2000-02-10'
FixedInVersion: 8.3b2
ClosedDate: '2000-10-25'

Name:
Bryan Oakley

Comments:
this seems to be a bug in many versions, dating back to 7.6, at least.

ReproducibleScript:
set s1 [clock scan ""]
set s2 [clock seconds]

puts "result of 'clock scan \"\"': $s1 ([clock format $s1])"
puts "result of 'clock seconds': $s2 ([clock format $s2])"

ObservedBehavior:
with the above script I'm seeing output similar to the following. Notice the two times are roughly an hour and fourteen minutes apart.

result of 'clock scan ""': 950046240 (Tue Feb 08 15:44:00 Central Standard Time
2000)
result of 'clock seconds': 950046240 (Tue Feb 08 16:58:29 Central Standard Time 2000)

DesiredBehavior:
[clock scan ""] should either return an error, or the current time.

According to the manpage, [clock scan ""] is legal, as the man page states "the dateString consists of zero or mor specifications of the following form".

Fixed in 8.3b2 to return current day at 00:00.
-- 02/10/2000 hobbs

Discussion

  • Brent B. Welch

    Brent B. Welch - 2000-10-26
    • priority: 5 --> 2
    • status: open --> closed-fixed
     
  • Don Porter

    Don Porter - 2001-04-04
    • labels: 104236 --> 06. Time Measurement
    • summary: [clock scan ""] yields surprising results --> [clock scan ""] yields surprising results
     
MongoDB Logo MongoDB