Year 2038 problem

C and PASCAL (or any other high-level languages) in here please

Moderators: simonsunnyboy, Mug UK, Zorro 2, Moderator Team

Count
Atari nerd
Atari nerd
Posts: 48
Joined: Sat Sep 16, 2017 9:15 am
Location: Castrop-Rauxel, Germany

Year 2038 problem

Postby Count » Thu Oct 31, 2019 8:40 pm

With respect to library development, are there already any considerations regarding the Year 2038 problem? Of course, we are still about 18 years away from that incident, but we all know that we will then still be using our Ataris and emulators.

The GEMDOS clock can handle dates until December 31, 2107. That's far beyond our lifetimes, so I would appreciate a native C solution (e.g. 64-bit time_t or _time64_t). Because I consider Mintlib being the de-facto standard C library at the present time, I would like to know whether its development community has spent any thoughts on this topic.

ThorstenOtto
Atari Super Hero
Atari Super Hero
Posts: 981
Joined: Sun Aug 03, 2014 5:54 pm

Re: Year 2038 problem

Postby ThorstenOtto » Thu Oct 31, 2019 11:16 pm

Not yet. Lets speak about this in ~10 years, that gives us ~8 years to implement it ;)

Edit: you could also just treat time_t as unsigned long. That gives us another 68 years of thinking about it ;);)

Count
Atari nerd
Atari nerd
Posts: 48
Joined: Sat Sep 16, 2017 9:15 am
Location: Castrop-Rauxel, Germany

Re: Year 2038 problem

Postby Count » Fri Nov 01, 2019 11:42 am

ThorstenOtto wrote:you could also just treat time_t as unsigned long. That gives us another 68 years of thinking about it ;);)

Yes, but in that case you will lose the years from 1902 to 1969 which would lead to me never being born. 8O


Social Media

     

Return to “C / PASCAL etc.”

Who is online

Users browsing this forum: No registered users and 5 guests