Yes I'm aware caesar, but that's only any use if the code for two or more switch values require the same code. All the values in the script above have different code.
I wouldn't mind some explanation of why my Windrop bot rolls extra days over into the next month rather than returning an invalid date. Seems absurd.
.tcl [clock scan 31-February-2011]
Tcl error: unable to convert date-time string "31-February-2011"
Indeed, welcome to the new (improved??!) clock within tcl 8.5. Give it bogus dates, it will return bogus values. Give it the 35th of a month, it will wrap 4 or 5 days into the next month (those with 30/31 days). This is due to tcl8.5 requiring the -format command to implicitly tell it the format you are giving it when using scan. It will no longer allow 'free-form" guesses like tcl8.4 clock did. This is why you see it wrapping into March.
Code:
#The issueif {[catch {set datevalue [clock scan $date]}]} {return e8}
Code:
#The solutionif {[catch {set datevalue [clock scan $date -format "%d-%B-%Y"]}]} {return e8}
-format format
Specifies the desired output format for clock format or the expected input format for clock scan. The format string consists of any number of characters other than the per-cent sign (“%”) interspersed with any number of format groups, which are two-character sequences beginning with the per-cent sign. The permissible format groups, and their interpretation, are described under FORMAT GROUPS.
Statistics: Posted by speechles — Mon Mar 07, 2011 1:50 pm
]]>
(März vs. March and so on... it only works on month which are similar in spelling like august, september,...)
