[Octave-bug-tracker] [bug #59979] Unexpected format for output from datevec

[Markus Mützel]

Follow-up Comment #21, bug #59979 (project octave):

Matlab moved away from these function and uses datetime and duration objects
now.
I believe Andrew Janke has worked on that.

Maybe we should just abandon these functions and try to get the more modern
types that better describe a date or a duration.

But if someone wants to try to get this function to better mimick what Matlab
returns, I'll be happy to run tests or review.

Octave seems to implement the carry-over rules correctly from datevectors to
datestrings (although it needs an additional step through `datenum`):

>> datestr(datenum([2009 22 03 00 00 00]))
ans = 03-Oct-2010
>> datestr(datenum([2010 07 -05 00 00 00]))
ans = 25-Jun-2010


IIUC, this report is not about carry-over behavior but about rounding
behavior.

Fwiw, in Matlab R2020b:

>> datevec(datenum([2021 01 02 00 00 59.9999]))

ans =

   1.0e+03 *

    2.0210    0.0010    0.0020         0         0    0.0600



    _______________________________________________________

Reply to this item at:

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

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