[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on
From: |
Philip Nienhuis |
Subject: |
Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW |
Date: |
Tue, 30 Nov 2010 20:00:48 +0100 |
User-agent: |
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.15) Gecko/20101027 SeaMonkey/2.0.10 |
Hi Tatsuro
Tatsuro MATSUOKA wrote:
> Hello
>
> Sorry for my late response.
> With http://octave.1599824.n4.nabble.com/file/n3049477/datestr.m, the error
> in time.cc from datestr
> (datenum (1969, 1, 1), 0) has been disappeared.
>
> I do not know this correction is preferable for the octave itself but at
> least solve the bug.
Yes.
But mind you, this version of datestr.m has probably been deprecated for
a reason.
Perhaps it was for bugs with correct interpretation of daylight saving
time?
If that doesn't matter for you (like it doesn't for me), this old
version is good enough.
> Perhaps correction of mktime on MinGw is preferable but I do not enough
> knowledge and time to fix
> this.
I don't think mktime() as it stands is a good basis. Some other solution
(not based on elapsed number of seconds since some epoch) is desired.
P.
- datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW, Tatsuro MATSUOKA, 2010/11/16
- Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW, Liam Groener, 2010/11/16
- Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW, Tatsuro MATSUOKA, 2010/11/17
- Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW, Philip Nienhuis, 2010/11/18
- Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW, John W. Eaton, 2010/11/18
- Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW, Tatsuro MATSUOKA, 2010/11/29
- Re: datestr (datenum (1969, 1, 1), 0) does not work on octave-3.3.51+ on MinGW,
Philip Nienhuis <=