|
| From: | Markus Mützel |
| Subject: | [Octave-bug-tracker] [bug #60647] datevec(730972.1249999999) |
| Date: | Thu, 20 May 2021 11:21:34 -0400 (EDT) |
| User-agent: | Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/90.0.4430.212 Safari/537.36 Edg/90.0.818.62 |
Update of bug #60647 (project octave):
Category: None => Interpreter
Item Group: None => Matlab Compatibility
Status: None => Confirmed
Operating System: GNU/Linux => Any
_______________________________________________________
Follow-up Comment #1:
This is very similar to bug #59979.
Matlab seems to (arbitrarily?) impose a limit to the precision of input to
date functions.
I'm still undecided if that is a good thing or not.
The output for me with Octave 6.2.0 on Windows:
>> datevec(730972.1249999999)
ans =
2.0010e+03 5.0000e+00 1.0000e+00 2.0000e+00 5.9000e+01
6.0000e+01
>> ans(end)-60
ans = -1.5259e-05
The given time corresponds to approximately 15 µs before 3 am on 2001-May-01.
So, technically that isn't at 3 am yet...
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?60647>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
| [Prev in Thread] | Current Thread | [Next in Thread] |