[Tcl-bugs] [ tcl-Bugs-1929060 ] [clock scan] gets confused by [clock format]

[SourceForge.net <no...@so...>]

Bugs item #1929060, was opened at 2008-03-29 21:18
Message generated for change (Settings changed) made by kennykb
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1929060&group_id=10894

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: 06. Time Measurement
Group: current: 8.5.2
>Status: Pending
>Resolution: Duplicate
Priority: 5
Private: No
Submitted By: Andy Goth (andygoth)
Assigned to: Kevin B KENNY (kennykb)
Summary: [clock scan] gets confused by [clock format]

Initial Comment:
Run the following two commands in a fresh tclsh:

% clock format 0 -format "%D %H:%M:%S"
% clock scan "01/01/1970 00:00:00"\
   -format "%m/%d/%Y %H:%M:%S"

The following error is returned:

input string does not match supplied format
    while executing
"$scanner $string $base $timezone"
    (procedure "::tcl::clock::scan" line 82)
    invoked from within
"clock scan "01/01/1970 00:00:00"\
   -format "??/??/210 H:M:0x00000000""
    ("uplevel" body line 1)
    invoked from within
"uplevel #0 clock\ scan\ \"01/01/1970\ 00:00:00\"\\\n\ \ \ -format\ \"??/??/210\ H:M:0x00000000\""

Now start another tclsh and run the following three commands:

% clock scan "01/01/1970 00:00:00"\
   -format "%m/%d/%Y %H:%M:%S"
% clock format 0 -format "%D %H:%M:%S"
% clock scan "01/01/1970 00:00:00"\
   -format "%m/%d/%Y %H:%M:%S"

No error is returned; instead, 21600 is returned, as expected.

It looks like running [clock format] before the first [clock scan] can potentially screw up the internal state of the [clock] command.

This problem was originally discovered by Peter Turner.  His email address is similar to Peter.Turner@com!forthc  .  He experienced it when using my timebox command, found at http://andy.junkdrome.org/devel/timebox/ .

----------------------------------------------------------------------

>Comment By: Kevin B KENNY (kennykb)
Date: 2008-03-29 23:13

Message:
Logged In: YES 
user_id=99768
Originator: NO

Can you verify that you're actually running one of 
the 8.5.2 release candidates? Your symptoms appear to
duplicate [Bug 1902423], for which a fix went it on
2008-02-27.  I see the described behaviour in 8.5.0,
but cannot reproduce it in either 8.5.2rc3 or the HEAD.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=110894&aid=1929060&group_id=10894