[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Octave-bug-tracker] [bug #41286] datestr() returns wrong results if one

From: Elmar Leson
Subject: [Octave-bug-tracker] [bug #41286] datestr() returns wrong results if one of input params is int32
Date: Mon, 20 Jan 2014 14:33:16 +0000
User-agent: Mozilla/5.0 (Windows NT 5.1; rv:26.0) Gecko/20100101 Firefox/26.0


                 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



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)
> 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))
> 2014-02--9 % day is negative!!!
is out of range.

My request: datestr must work with all integer formats.

Current workaround: 


Reply to this item at:


  Nachricht gesendet von/durch Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]