year2038

I would like to print or extract year/month/day values. I don't want to use time_t because of the year 2038 problem, but all examples I found on the Internet use it to convert time_point to tm . Is there a simple way to convert from time_point to tm (preferably without boost )? An implementation like timesub from libc would be my last resort: http://www.opensource.apple.com/source/Libc/Libc-262/stdtime/localtime.c Edit: After reading the suggested links and doing some more research, I came to the following conclusion. Using time_t where it is 64bit long is ok (for most purposes). Using Boost

How to convert Epoch to DateTime SQL Server if epoch exceeds the year 2038? Answer in Convert Epoch to DateTime SQL Server will not work. Example: SELECT DATEADD(ss, 2713795200000 / 1000, '19700101') Thu, 30 Dec 2055 16:00:00 GMT DATEADD function assumes an INT as an increment to your date, to bypass the limitation of INT you can either reduce the precision of your epoch, or do a slightly complex code to retain the precision of your epoch. This reduces the precision to minutes: SELECT DATEADD(MINUTE,@YourEpoch/60/1000, '1/1/1970') This one splits your epoch to days and milliseconds and then

Year 2038 Bug is all over the web, But this seems to be a unix issue. How will this affect java Date ? What makes you think it does? Java's Date class stores a 64-bit long (not 32-bit, as with Y2K38). It also stores milliseconds, which decreases the range, but only slightly (equivalent of ~10 bits). In Java, we have the year 292278994 bug. I don't believe it will impact the Java Date class as for as the programmer is concerned. It's already using 64-bit values. I can see it being a problem if you're using a data store that still uses 32-bit values. I don't expect to see too many 32-bit OSes

I just found out, running a calendar script, that timestamps in PHP has a limit to 2038. What does it really mean? Why is it 2038 instead of 2050 or 2039? Why a limit if timestamps just count seconds from a given date (1970)? The limit is imposed by the 4 byte signed integers that most C libraries use for representing that count. Quick math (assumes 365 day years, not exactly correct): 2147483648 seconds ~ 68.1 years This also implies a lower limit of ~1900. Some libraries have started to introduce 64 bit epoch counts, but they are few and far between for the moment. The maximum value of a 32

I would like to think that some of the software I'm writing today will be used in 30 years. But I am also aware that a lot of it is based upon the UNIX tradition of exposing time as the number of seconds since 1970. #include <stdio.h> #include <time.h> #include <limits.h> void print(time_t rt) { struct tm * t = gmtime(&rt); puts(asctime(t)); } int main() { print(0); print(time(0)); print(LONG_MAX); print(LONG_MAX+1); } Execution results in: Thu Jan 1 00:00:00 1970 Sat Aug 30 18:37:08 2008 Tue Jan 19 03:14:07 2038 Fri Dec 13 20:45:52 1901 The functions ctime(), gmtime(), and localtime() all