On Sat, Apr 11, 2009 at 11:13 PM, King InuYasha <ngompa13(a)gmail.com> wrote:
Then what DOES NT use to calculate time?
Win32 uses SYSTEMTIME and FILETIME structures to store and calculate
the time/date which if I recall correctly user a large int to store
and calculate time since 1970. No problem with space there. See
http://msdn.microsoft.com/en-us/library/ms725473(VS.85).aspx
I am curious if the posix subsystem has any problems with the 2038
bug. Most likely not as it should use the correct native functions
internally. Any POSIX application that expects normal 32bit time_t
under Services for Unix or Subsystem of Unix applications would still
be affected. Again, your talking about 1/2 of .0001% of all
applications running on Windows though. Maybe a few other applications
that have been ported over using a third party static libc doing its
own timekeeping would also be affected but like Alex and Ged have
pointed out, its a Unix problem. Yes they do exist, Unix, Linux and
friends are not perfect.
I wonder what Apple's 2038 plans are. Most likely to kill support for
32bit long before ;)
--
Steven Edwards
"There is one thing stronger than all the armies in the world, and
that is an idea whose time has come." - Victor Hugo