[Octave-bug-tracker] [bug #51340] datevec jump hour on 29/03/2009 02:*

[Mike Miller]

Follow-up Comment #10, bug #51340 (project octave):

What should the behavior of datevec be when given an invalid time string?

In my time zone there is no such thing as "2017-03-12 02:00:00". The GNU date
program correctly reports an error. The next time increment after "2017-03-12
01:59:59" is "2017-03-12 03:00:00".

In your example and in your time zone, "29/03/2009 02:10:05" is an invalid
time specification.

Would you prefer Octave to fold the time over by one hour the way it does now,
or throw an error when given an invalid time string like this?

Or were those times recorded in UTC and you should be setting your local time
zone to UTC before processing them?

    _______________________________________________________

Reply to this item at:

  <http://savannah.gnu.org/bugs/?51340>

_______________________________________________
  Message sent via/by Savannah
  http://savannah.gnu.org/