< Previous by Date Date Index Next by Date >
< Previous in Thread Thread Index Next in Thread >

RE: [reSIProcate] y2k38


To follow up and confirm, int's will remain 32bits on 64-bit systems.  Other
64-bit related issues can be found here:

http://www.intel.com/cd/ids/developer/asmo-na/eng/technologies/64bit/197664.
htm?page=2



-----Original Message-----
From: resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx
[mailto:resiprocate-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of Justin
Matthews
Sent: Thursday, April 28, 2005 6:31 PM
To: 'resiprocate'
Subject: [reSIProcate] y2k38

I noticed the following in the ares library that deals with time_t values
that are cast to int's.  On intel/windows 64-bit platforms I believe that
int will remain 4 bytes, but time_t has changed to __int64( since visual
studio 2005) to handle the y2k38 problem (seconds since midnight jan 1, 1970
UTC time).  To be on the safe side it would be a good idea to not cast
time_t values to int's.

-Justin


----ares_process.c----
static void process_answer(ares_channel channel, unsigned char *abuf,
                           int alen, int whichserver, int tcp, /*int*/time_t
now);


---ares_timeout.c----

struct timeval *ares_timeout(ares_channel channel, struct timeval *maxtv,
                             struct timeval *tvbuf)
{
  struct query *query;
  time_t now;
  time_t /*int*/ offset, min_offset;


_______________________________________________
resiprocate-devel mailing list
resiprocate-devel@xxxxxxxxxxxxxxxxxxx
https://list.sipfoundry.org/mailman/listinfo/resiprocate-devel