Actually, UNIX time is a signed 32-bit number, so it only makes it to 2038. Microsoft and others will have some fun then!! As for me, I don't need the length of the 64bit, but I do want to make it past 2038, so that's why I initially chose int64. However, now that I think of it, it would make it easier if I used int32 and made it unsigned. That way it would last until 2106 or so. (BTW, to be compatible w/ UNIX time (whether signed or not), the epoch time is 1/1/1970 0:0:0, so I've already lost 35 years!) Thanks for the suggestion. -Mark
-----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Garst R. Reese Sent: Friday, July 08, 2005 9:54 AM To: [email protected] Subject: Re: [Mspgcc-users] Re: time.h ? Hmm, 32 bits will count the seconds between now and 2141. Do you really need unix time? Just a thought, Garst Stokes, Mark wrote: >I have no idea what RTAI and DCF77 are but I am interested specifically in a >long long >unix time (my product should last longer than 2038) and must have the ability >to "edit" >it by a human in the setup (not during normal operation). The actual _use_ of >the unix >time will be simply output to the datalogger (no conversions). > >-Mark > > ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Mspgcc-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mspgcc-users
