[Octave-bug-tracker] [bug #41286] datestr() returns wrong results if one of input params is int32

[Elmar Leson]

URL:
  <http://savannah.gnu.org/bugs/?41286>

                 Summary: datestr() returns wrong results if one of input
params is int32
                 Project: GNU Octave
            Submitted by: el77
            Submitted on: Mo 20 Jan 2014 14:33:15 GMT
                Category: Octave Function
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: Incorrect Result
                  Status: None
             Assigned to: None
         Originator Name: el77
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                 Release: 3.6.4
        Operating System: Microsoft Windows

    _______________________________________________________

Details:

I got wrong results with datestr(). Was hard to find, because the input date
of datest() was generated by datenum(). But if one of the input parameters of
datenum() is of int32 format, the function returns int32. That doesn't work
with datestr().

dat = datenum(2014,01,20)
datestr(dat,29)
> 2014-01-20

works correctly. But
dat = datenum(int32(2014),01,20) or 
dat = datenum(2014,int32(01),20) or
dat = datenum(2014,01,int32(20))
datestr(dat,29)
> 2014-02--9 % day is negative!!!
is out of range.

My request: datestr must work with all integer formats.

Current workaround: 
datestr(double(dat),29)




    _______________________________________________________

Reply to this item at:

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

_______________________________________________
  Nachricht gesendet von/durch Savannah
  http://savannah.gnu.org/