[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #36563] datevec compatability
From: |
Alexander Barth |
Subject: |
[Octave-bug-tracker] [bug #36563] datevec compatability |
Date: |
Mon, 04 Jun 2012 11:11:51 +0000 |
User-agent: |
Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:10.0.1) Gecko/20100101 Firefox/10.0.1 |
Follow-up Comment #7, bug #36563 (project octave):
In the revised patch (datevec-new.patch), I added support for the format
21,22, 25, 26 29 and 31.
I tested the code and I got the same results as in matlab R2010a
(test_datevec.m).
However, formats 12,24,25 and 28 give quite strange (bogus?) result in
matlab:
datevec('Mar00',12) % mmmyy
ans = 2012 2 29 0 0 0
datevec('01/03/2000',24) %dd/mm/yyyy,
ans = 2000 1 3 0 0 0
datevec('00/03/01',25) %yy/mm/dd
ans = 101 1 3 0 0 0
datevec('Mar2000',28) %mmmyyyy
ans = 2017 8 21 0 0 0
Can somebody with a newer version of matlab confirm this?
Format 24 gives the same results in octave 3.6.1 (with or without patch) than
in matlab. However, day and month are reversed according to documentation.
(file #25981, file #25982)
_______________________________________________________
Additional Item Attachment:
File name: datevec-new.patch Size:1 KB
File name: test_datevec.m Size:3 KB
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?36563>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/