KDateTime::currentUtcDateTime()

[Thiago Macieira]

Nicolas Goutte wrote:
>On Saturday 29 July 2006 10:09, Thiago Macieira wrote:
>> Nicolas Goutte wrote:
>> >Thinking further, I have found one possible reason: using the Windows
>> > API avoids the year 2038 bug if time_t is 32 bit long.
>>
>> And since Windows 64-bit is an IL32 P64 architecture, long is always
>> 32-bit.
>
>Well, then the other uses of time_t in KDE should go away in KDE4.
>
>On the other side, we have still some 30 years to fix KDE. :-)

We should use time_t whenever a time_t is expected: a number of seconds 
since 01-01-1970 midnight UTC. If Windows compilers choose to perpetuate 
time_t as 32-bit, it's their problem. They could just as well define it 
to be int64_t.

But we should NOT mix time_t and long and hope that they are equivalent.

-- 
  Thiago Macieira  -  thiago (AT) macieira.info - thiago (AT) kde.org
    PGP/GPG: 0x6EF45358; fingerprint:
    E067 918B B660 DBD1 105C  966C 33F5 F005 6EF4 5358
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20060730/a7816c88/attachment.sig>