Liste des Groupes | Revenir à col advocacy |
On Wed, 2 Oct 2024 00:07:15 -0400, 186282@ud0s4.net wrote:*IF* ....
If the programmer follows ISO/POSIX standards then>>
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 ......
>
it will all automatically become 64-bit because all
libc time/date functions are based on time_t, which
is an integer defined in the libc headers.
Some filesystem timestamps may still be 32-bit but'C' doesn't go back to the 50s. FORTRAN does though,
that shouldn't be hard to fix. If the filesytem is
in wide usage it should be fixed already.
The swamp just gets deeper and deeper.Most C source code from the 1950's, or even the 1990's,
>
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.
>
would not on run on current 64-bit systems anyway,
irrespective of date/time functions.
I have had to convert code from the early 2000's justTherein lies a big part of The Problem - so MUCH
to make it run on my machine. The change from 32 to
64 bit processors forced many, many packages to be
rewritten.
But you are correct. Lot's of code won't make it butIt's not just the desktops ... it's everything they
for desktop GNU/Linux workstations this code is largely
irrelevant and may be irrelevant elsewhere as well.
Les messages affichés proviennent d'usenet.