[Octave-bug-tracker] [bug #36954] datenum / datevec convert date-time string incorrectly during hour lost to DST

[Philip Nienhuis]

Update of bug #36954 (project octave):

                  Status:               Need Info => Postponed              

    _______________________________________________________

Follow-up Comment #42:

Too bad that Octave's behavior suffered from a regression compared to Mike's
fix in comment #34.
Closing this bug because (interpreted in my words) "it is documented that
Octave behaves buggy here" feels a bit awkward.
I wonder what caused this regression. Currently I have no time to sort it out;
but within a few months I hope to have time to return to my tidal hobby
project where I hit this (and hard - it was a big PITA for me and a good
reason to resort to the proprietary competition that does it correctly).

So I've just set status to "postponed". Hopefully not for too long.

That said, IMO datevec.m is an opaque and entangled piece of code. I've hit
some strange issues with my patch #9964 and I have trouble deducing what
datevec's code actually does vs. what it is supposed to be doing.

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?36954>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/