Built-in date functions ... qwirk or bug?

[Dylan Raethel]

Thanks Pat and Alan.
Sorry the cut n' paste needed manipulation - I'm able to stick the script
straight into quickscript from the email on my Win2k system.
Also sorry for not considering date format by locale in the posted example
script.

The date coercion point is well received but makes no difference - in fact
the date.get function uses the clock.now() call in its docserver example:
Examples date.get (clock.now (), @day, @month, @year, @hour, @minute,
@second) see: http://docserver.userland.com/date/get
and it is the result of the clock.now() call that was edited to provide the
timeToCheck values in the script sample.  

(Incidentally Alan, I used the date that you altered ("March 26 2003,
7:11:11 AM") and had no coercion problems but still had the same strange
results.  You don't mention your OS but I'm guessing Mac, as I have found
that things are fine on the Mac.

Any WinOS folk wanna try ratifying this under Frontier or Radio?

The point of the query is that the date.get function (when given a date
type) for times from 1 am to 7.59 am return 13 to 19 as the hour, the times
0:00 to 0:59 and  8am to 11:59am return 0, and 8 to 11 as expected   (for
me, and a few others I've asked at different institutions - perhaps it's a
New Zealand thing:-) 


**********************************************************************
This email is not an official statement of the Waikato
Regional Council unless otherwise stated.
Visit our website http://www.ew.govt.nz
**********************************************************************