[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-devel
Subject:    Re: 64-bit time_t
From:       Stephan Kulow <coolo () kde ! org>
Date:       2003-09-29 8:13:12
[Download RAW message or body]

Am Montag, 29. September 2003 10:01 schrieb Adriaan de Groot:
> does the fix, by using the right pointer size and then assigning a 64-bit
> quantity to a 32-bit field (might cause a warning, I haven't tried).
It would give a warning on 64bit only - and it's their decision to leave the
32bit field, so they shouldn't be worried too much about logins after 2038 ;)

>
> Now the question is: where to fix this? I could keep the patches local to
> FBSD, or I can commit in KDE CVS. It's a few cycles wasted here and there
It's not wasted per se, it's POSIXly correct code.

> where time_t is 32-bit, but hey. It's also a little code convolution that
> needs to be documented all over the place.
Do we have so many places reading utmp?

Greetings, Stephan

-- 
Pace Peace Paix Paz Frieden Pax Pokój Friður Fred Béke 和平
Hasiti Lapé Hetep Malu Mир Wolakota Santiphap Irini שלום Peoch
Shanti Vrede Baris Rój Mír Taika Rongo Sulh Py'guapy 평화
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<

[prev in list] [next in list] [prev in thread] [next in thread]