[Qt-interest] New Date and Time Features in Qt5?

[Atlant Schmidt]

Thiago:

> Let's try again: please name two systems where
> Qt runs where the OS reports 61-second minutes.

  I don't have any at hand, but are you saying you
  don't *EVER* want Qt to be used in:

    o Atomic clocks
    o GPS Receivers
    o Astronomical applications?

  Any of those are *CERTAINLY exposed to Leap Seconds
  several times a year (on average, though not lately).
  And, in fact, so is any application that actually
  tries to handle time in an completely-accurate fashion
  (financial trading apps, etc.)

  Perhaps you should join the movement that's trying
  to stamp-out Leap Seconds in favor of the once-
  every-900-years (or so) Leap Hour? ;-) That idea
  would certainly make life easier for us programmers!

                        Atlant

-----Original Message-----
From: qt-interest-bounces+aschmidt=dekaresearch.com at qt.nokia.com [mailto:qt-interest-bounces+aschmidt=dekaresearch.com at qt.nokia.com] On Behalf Of Thiago Macieira
Sent: Friday, May 13, 2011 15:07
To: qt-interest at qt.nokia.com
Subject: Re: [Qt-interest] New Date and Time Features in Qt5?

On Friday, 13 de May de 2011 14:24:20 Atlant Schmidt wrote:
> > > * support for leap seconds (=> minutes with 61 seconds)
> >
> > Please point me to two systems where this is used.
>
>   (I'm not the person making the request but) I think
>   what I'd want is assurances that Qt has been tested
>   in the presence of Leap Seconds and does reasonable
>   things with those exceptional time values. That is,
>   nothing should SegFault, time formatters should
>   display 23:59:60, delta time calculations should
>   work accurately, and so forth.

Let's try again: please name two systems where Qt runs where the OS reports
61-second minutes.

--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
  Senior Product Manager - Nokia, Qt Development Frameworks
      PGP/GPG: 0x6EF45358; fingerprint:
      E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358

This e-mail and the information, including any attachments, it contains are intended to be a confidential communication only to the person or entity to whom it is addressed and may contain information that is privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender and destroy the original message.

Thank you.

Please consider the environment before printing this email.