@cm0002@lemmy.world to Programmer Humor@programming.dev • 6 months agoY-10Klemmy.mlimagemessage-square13arrow-up1279cross-posted to: programmerhumor@lemmy.ml
arrow-up1279imageY-10Klemmy.ml@cm0002@lemmy.world to Programmer Humor@programming.dev • 6 months agomessage-square13cross-posted to: programmerhumor@lemmy.ml
minus-square@pimeys@lemmy.nauk.iolinkfedilink21•6 months agoAnd not using 32-bit integers to calculate time. Which is still a thing in many many many codebases written in C or C++…
minus-squareJustEnoughDuckslinkfedilink2•6 months ago32 bit embedded processors us a lot of 32 bit time, though i am not sure if date time libraries in SDKs have been updated to use 64 bit for time.
minus-square@pimeys@lemmy.nauk.iolinkfedilink3•6 months agoLinux kernel updated to 64 bit time quite recently. In 2038 I can guarantee somebody in a very serious business is still using an ancient RHEL and will have issues.
And not using 32-bit integers to calculate time. Which is still a thing in many many many codebases written in C or C++…
32 bit embedded processors us a lot of 32 bit time, though i am not sure if date time libraries in SDKs have been updated to use 64 bit for time.
Linux kernel updated to 64 bit time quite recently. In 2038 I can guarantee somebody in a very serious business is still using an ancient RHEL and will have issues.