[Octave-bug-tracker] [bug #64563] datevec: "mmm dd yyyy" matched instead of "mmmyyyy" standard format

[Philip Nienhuis]

Follow-up Comment #12, bug #64563 (project octave):


> I'm not sure if it is possible in principle that datevec can correctly match
all formats that have a numeric identifier in datestr.
Yeah I'm also unsure (just started investigating, then real life stepped in)
but we can at least try to match as much as possible (or reasonable).
>It took me a while to notice that "AUG2013" can be matched by the pattern
'mmm dd yyyy'.
That's what this bug report is about. I suppose datevec.m should catch & if
needed preprocess input before handing over to strptime(). Easiest is to
provide a new format matching one in datestr.m.

strptime() is a beast and on top of that its behavior is partly
implementation-defined (I hit that in the past that when trying to fix
daylight saving time issues). So yes, surprises are due ...

I'm not so afraid of surprises if they pertain to undocumented behavior.
I'm more concerned (but not _that_ much) with consistency of functions that
provide, or implicitly or explicitly suggest to provide, each other's inverse,
like datestr.m and datevec.m.



    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?64563>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/