| Ticket UUID: | 2837916 | ||
| Title: | clock scan 01/2010 -format %m/%Y returns wrong result | ||
| Type: | Bug | Created on: | 2009-08-14 22:33:32 |
| Submitter: | flatworm | Assigned to: | ferrieux |
| Subsystem: | 06. Time Measurement | Severity: | |
| Priority: | 5 Medium | Last modified: | 2011-11-16 00:44:53 |
| Status: | Open | Closed by: | |
| Resolution: | None | Closed on: | |
| Version: | obsolete: 8.6b1 | ||
| Description: | ||||
[clock format [clock scan 01/2010 -format %m/%Y]] returns Sat Aug 15 00:00:00 MSD 2009 while it was supposedly requested to scan Jan 01 of year 2010, time 00:00:00. Instead, it seems to return the current date with the time part reset to 00:00:00. Reproducible on Debian (Linux) on 8.5.3 and the current HEAD. | ||||
| User Comments: | ||||
kennykb added on 2009-10-29 07:44:01:
Alex, I seem to recall you thinking that you had a proposal for how to fix this. I'm quite nervous about accepting underspecified dates because of the inherent ambiguities, but I"d be happy to review a concrete proposal, if you can come up with one. jeremy_c added on 2011-11-16 00:44:53:
I have the same problem with: "clock scan 2011/05 -format %Y/%m" .. I'd propose that if an element is missing just take today's element. If that has adverse side effects then I would suggest that if the -format parameter is supplied and does not include a full date that an error should be returned not an arbitrary date. | ||||
