[Octave-bug-tracker] [bug #64563] datevec: undefined mmmddyy partially matched instead of mmmyyyy standard format

[Markus Mützel]

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

Yeah, I quoted that part on purpose. I was hoping a native speaker could come
up with something more technical. Maybe, something along the lines of:
> If no format string is provided, heuristics are used to guess the input
format.

And if that is not clear enough, we could follow with something like:
> These heuristics might not give the expected result.

Not sure which inconsistency you mean.
In Matlab R2023a:

>> dstr = datestr (datenum ([2013, 8, 1, 0, 0, 0]), 28)
dstr =
    'Aug2013'
>> datevec(dstr, 'mmmyyyy')
ans =
        2013           8           1           0           0           0


For the roundtrip to work, you'd need to use the same (or equivalent) format
specifiers in both directions.
Or if you don't want to use format specifiers, you must not use them in both
directions:

>> dstr = datestr (datenum ([2013, 8, 1, 0, 0, 0]))
dstr =
    '01-Aug-2013'
>> datevec(dstr)
ans =
        2013           8           1           0           0           0


Format "29" was a typo. I meant to write "28". Which Matlab incompatibility
are you referring to?




    _______________________________________________________

Reply to this item at:

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

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