72
submitted 6 months ago by neme@lemm.ee to c/linux@programming.dev
you are viewing a single comment's thread
view the rest of the comments
[-] vane@lemmy.world 8 points 6 months ago

It's just dropping them from distribution, I think it's a good idea to separate this codebase before 2038.

[-] Quetzalcutlass@lemmy.world 2 points 6 months ago* (last edited 6 months ago)

The Unix epoch problem is completely unrelated to a program being 32-bit or not. The architecture affects the maximum addressable memory space, not the size of individual types. You could easily define and use a 128-bit type in a 16-bit environment, for example.

The epoch problem is simply due to a bad design call a long time ago - one that proved foundational and incredibly difficult to change once it'd become an entrenched standard. They could have made timestamps 64-bit at the time, and probably would have if they'd known their work would survive the several decades it'd take for that decision to pay off.

this post was submitted on 24 Jun 2025
72 points (96.2% liked)

Linux

10805 readers
533 users here now

A community for everything relating to the GNU/Linux operating system (except the memes!)

Also, check out:

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS