Sujet : Re: Can't Avoid That Shit Rust - Even On Gentoo
De : 186283 (at) *nospam* ud0s4.net (186282@ud0s4.net)
Groupes : comp.os.linux.advocacy comp.os.linux.miscDate : 02. Oct 2024, 05:07:15
Autres entêtes
Organisation : wokiesux
Message-ID : <Btycnd1FwtZrW2H7nZ2dnZfqnPednZ2d@earthlink.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
On 10/1/24 3:54 AM, Farley Flud wrote:
On Mon, 30 Sep 2024 19:40:06 -0000 (UTC), candycanearter07 wrote:
>
Then, people ignore the problem until it's right there.
For instance, the 2038 problem I'm betting will be ignored until 2035.
>
Hasn't the 2038 problem already been fixed?
GNU/Linux has had 64-bit time for many years already.
It's not just HAVING 64/128-bit vars. Gotta look
at every function, every line. The original pgmr
likely specified 32-bit vars for a of of the
date-related stuff because, well, datetime is
always 32 bit, right ? Hey, the cdates/mdates
on FILES too ......
The swamp just gets deeper and deeper.
There are kind of the literal gazillion bits of
code in dozens of languages created from the
late 1950s on that are inside apps/systems
everywhere today that in some way deal
with, depend on, datetimes.
In the ancient days, there was an ultra-nerd
named Bill Gates who used to participate in,
often win, contests to see who could code
some useful function in the very least number
of bytes/cycles. Bill was something of a hero
figure then. However, he wrote that code using
the ASSUMPTIONS of the day. Betcha there's
still some of his old code in modern systems.
As such, only "AI" is going to be able to deal
with such volume and diversity. It will have to
be trained to detect datetime operations and
literally re-write the relevant code.
And we'd better make/train it QUICKLY.