Ticket #2003 (closed feature request: wontfix)
The Data.Time.Format parser should be more liberal
| Reported by: | BjornBuckwalter | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Not GHC |
| Component: | libraries (other) | Version: | |
| Keywords: | Cc: | ||
| Operating System: | Unknown/Multiple | Architecture: | Unknown/Multiple |
| Type of failure: | Difficulty: | Unknown | |
| Test Case: | Blocked By: | ||
| Blocking: | Related Tickets: |
Description
I (Björn Buckwalter) wrote to the libraries list:
Is there a compelling reason to not make the formats in Data.Time.Format case-insensitive when parsing? This would apply to the months, weekdays, time zone. (I see there are already two formats %p and %P corresponding (confusingly) to AM/PM and am/pm respectively.)
What got me thinking about this is that I'm being supplied with dates on the format "26 DEC" which will not parse without munging. I suspect such situations are fairly common?
To which Björn Bringert replied:
I agree. The parser should be more liberal. I originally implemented rather faithful inverses of the formatting directives, but I don't really see any point in being very strict when parsing.
You are welcome to submit a patch for this, or at least a feature request in Trac to keep it from being forgotten.
