egghelp/eggheads community

Validating a date

2010-01-27T20:47:04-04:00

Sorry, yes you are correct speechless :-

[00:34] .tcl set test $tcl_platform(os)
[00:34] Tcl: Linux
[00:35] .tcl set test $tcl_version
[00:35] Tcl: 8.4
[00:35] .tcl set test [clock scan 13/33/10]
[00:35] Tcl error: unable to convert date-time string "13/33/10"

[00:32] .tcl set test $tcl_platform(os)
[00:32] Tcl: CYGWIN_NT-6.0
[00:32] .tcl set test $tcl_version
[00:32] Tcl: 8.5
[00:33] .tcl set test [clock scan 13/33/10]
[00:33] Tcl: 1296604800

In view of the pending 32 bit issue, I'm not entirely sure if it is a bright side or a not so bright side but I probably won't get to see 2038.

Thanks for the site Sir_Fz, I'll devise something along those lines most probably (that is one mean looking regexp).

Statistics: Posted by arfer — Wed Jan 27, 2010 8:47 pm

Re: Validating a date

2010-01-27T18:43:22-04:00

Arfer, are you sure you don't have that backwards? Tcl 8.5 should accept the bogus date and return a bogus value, while tcl8.4 should return the "unable to convert date/time string" reply.

Clock was changed in tcl8.5, see here.

.tcl set a [catch {set b [clock scan 1/1/10]}]
Tcl: 0
.tcl set a [catch {set b [clock scan 33/1/10]}]
Tcl: 1
.tcl set from [clock scan 13/33/10]
Tcl error: unable to convert date-time string "13/33/10"
.tcl set test [clock scan 1/1/37]
Tcl: 2114409600
.tcl set test [clock scan 1/1/38]
Tcl error: unable to convert date-time string "1/1/38"

Code:

 I am sp33chy, running eggdrop v1.6.17: 25 users (mem: 1481k). Online for 9 days, 01:26 (background) - CPU: 34:44 - Cache hit: 9.6% Admin: jesus Config file: eggdrop.conf OS: CYGWIN_NT-5.1 1.5.18(0.132/4/2) Tcl library: /cygdrive/f/windrop/lib/tcl8.4 Tcl version: 8.4.11 (header version 8.4.11)

A problem in the future will be that 32bit systems wont like the year 2038 very much..

Statistics: Posted by speechles — Wed Jan 27, 2010 6:43 pm

Validating a date

2010-01-27T16:43:20-04:00

Not sure if Tcl is affected by the regional settings of the running machine, but if so it could be that the date format on the latter machine is not %m/%d/%y.

After a quick Google search, I found this. You can try and and see if it's correct and then modify it to suite your needs.

Statistics: Posted by Sir_Fz — Wed Jan 27, 2010 4:43 pm

Validating a date

2010-01-27T16:28:00-04:00

I'm using the following to try to validate a date in the normal US form m?m/d?d/yy (by validate I mean assertain if such a date could exist) :-

Code:

if {[catch {set from [clock scan $date]} {  # error code} else {  # remainder of code}

I fully expected that an invalid date such as 13/33/10 would be caught by the above code.

My Eggdrop running Tcl 8.5 functions as I expected. Using similar code in the partyline yields :-

[20:12] .tcl set from [clock scan 13/33/10]
[20:12] Tcl error: unable to convert date-time string "13/33/10"

My Windrop running Tcl 8.4 does not function as expected, yielding the following in the partyline :-

[20:11] .tcl set from [clock scan 13/33/10]
[20:11] Tcl: 1296604800

I'm not sure if this a Tcl version issue or a Windows/Linux date/time issue or even a geographical issue or a combination thereof.

In any event, what (hopefully simplistic) code is recommended for validating dates that functions as expected irrespective of the bot type, Tcl version, operating system or geography.

Statistics: Posted by arfer — Wed Jan 27, 2010 4:28 pm