Tcl Source Code

clock scan accepts fairly wild dates, such as the 99th
of February 2005, but rejects the 100th of February ...
I haven't tried this on a leap year :)

I would expect it to error on such dates.

% clock scan 2005/02/99 -format %Y/%m/%d
1115647200
% clock scan 2005/02/100 -format %Y/%m/%d
input string does not match supplied format
% puts $tcl_version
8.5
% puts $tcl_patchLevel
8.5a2

File Deleted - 119462:

File Added - 119467: daysinmonth.tcl

Logged In: YES 
user_id=99768

A more obvious method to find the last 
day of the month in 8.5, by the way, is
to use [clock add], giving it 1 month
-1 day.  I've updated the attachment to
show both methods.

File Added - 119462: daysinmonth.tcl

Logged In: YES 
user_id=99768

This behavior is by design; [clock scan] 
will accept any number that matches the 
format group, even if it is outside the range.
This is actually useful on occasion.  In fact,
one of the ways to determine the number
of days in a month is to give [clock scan]
day zero of the following month (which might
be month thirteen).  The attached file gives
the idea.

Logged In: YES 
user_id=19214

I only discovered this behavior because I was relying on
[clock scan]'s error to construct a calendar.

I was iterating over day and scanning $day/$month/$year
until it errored saved me having to remember how many days
in each month, correcting for leap years and centuries.