| Ticket UUID: | 1639435 | |||
| Title: | Clock scan | |||
| Type: | Bug | Version: | obsolete: 8.5a6 | |
| Submitter: | vampiera | Created on: | 2007-01-19 11:01:29 | |
| Subsystem: | 06. Time Measurement | Assigned To: | kennykb | |
| Priority: | 5 Medium | Severity: | ||
| Status: | Closed | Last Modified: | 2007-02-13 10:54:22 | |
| Resolution: | Invalid | Closed By: | kennykb | |
| Closed on: | 2007-02-13 03:54:22 | |||
| Description: |
problem to scan an invalid date. example (in test.tcl attached): 2008-14-20 becomes 2009-02-20 without any error | |||
| User Comments: |
kennykb added on 2007-02-13 10:54:22:
Logged In: YES user_id=99768 Originator: NO That's not a bug; that's a feature. We deliberately allow month and day numbers out of range because they make certain calculations easier: for instance: 2007-03-00 is the last day of February; 2007-01-00 is the last day of 2006, and so on. As you observed, a month number of 14 is interpreted as February in the following year. It seems strange, but turns out to be convenient. vampiera added on 2007-01-19 18:01:29: File Added - 212037: test.tcl | |||
Attachments:
- test.tcl [download] added by vampiera on 2007-01-19 18:01:29. [details]