[Octave-bug-tracker] [bug #36563] datevec compatability

[Rik]

Update of bug #36563 (project octave):

                  Status:                    None => Need Info              

    _______________________________________________________

Follow-up Comment #3:

Which version of Matlab was tested?  And do we want to follow their behavior
or their documentation?

The documentation for datevec
(http://www.mathworks.com/help/techdoc/ref/datevec.html) for release 2012A is
very specific about which formats are supported.

Quoting the documentation:

"DateVector = datevec(DateString) converts date string DateString to date
vector V. Input argument DateString must be in one of the date formats 0, 1,
2, 6, 13, 14, 15, 16, or 23 as defined in the section . This calling syntax is
provided for backward compatibility, and is significantly slower than the
syntax which specifies the format string. If the format is known, the V =
datevec(DateString, FieldSpecIn) syntax is recommended."

The list of formats can be found here
(http://www.mathworks.com/help/techdoc/matlab_prog/bspgcx2-1.html) with the
section title "Numeric Identifiers for Predefined Formats".

As a first step, I think it would be useful if someone with access to a modern
version of Matlab could verify all 32 formats using the examples in the table
of Predefined Formats.

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?36563>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/