[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-bug-tracker] [bug #36587] datenum gives wrong result for int32 i
|
From: |
Randy |
|
Subject: |
[Octave-bug-tracker] [bug #36587] datenum gives wrong result for int32 input. |
|
Date: |
Tue, 05 Jun 2012 22:43:14 +0000 |
|
User-agent: |
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:12.0) Gecko/20100101 Firefox/12.0 |
Follow-up Comment #3, bug #36587 (project octave):
Matlab 7.8.0 (R2009a) gives the following output:
>> datestr(datenum(int32(2012), int32(6), int32(1)))
??? Error using ==> datenum at 174
DATENUM failed.
Caused by:
Error using ==> datenummx
The datenummx function only accepts double arrays.
>> datestr(datenum(2012, 6, 1))
ans =
01-Jun-2012
>> x = datenum(int32(2012), int32(6), int32(1))
class (x)
??? Error using ==> datenum at 174
DATENUM failed.
Caused by:
Error using ==> datenummx
The datenummx function only accepts double arrays.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?36587>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/