Title: Time traveling in the Year 2038
Abstract:
The Unix Epoch time is a system for representing time as the number of seconds elapsed since Epoch, internally stored as a signed integer value. As you might already see, this imposes a restriction on the range of values that can be stored. For 32-bit machines, at 03:14:07AM UTC on the 19th of January 2038 will be the end of time, Cue ominous music, as the signed notation would make the time roll back to Friday the 13th ;), December 1901.
In this post, let's discuss similar situations, existing solutions what could possibly go wrong.
Who is your target audience with this post? Be as specific as you can.
All programmers who deal with time in their programs or might be interested in proposing a solution (no universally accepted answer exists as of right now).
Title: Time traveling in the Year 2038
Abstract:
The Unix Epoch time is a system for representing time as the number of seconds elapsed since Epoch, internally stored as a signed integer value. As you might already see, this imposes a restriction on the range of values that can be stored. For 32-bit machines, at 03:14:07AM UTC on the 19th of January 2038 will be the end of time, Cue ominous music, as the signed notation would make the time roll back to Friday the 13th ;), December 1901.
In this post, let's discuss similar situations, existing solutions what could possibly go wrong.
Who is your target audience with this post? Be as specific as you can.
All programmers who deal with time in their programs or might be interested in proposing a solution (no universally accepted answer exists as of right now).