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 : 03. Oct 2024, 03:25:27
Autres entêtes
Organisation : wokiesux
Message-ID : <15ednSDYmsw3nWP7nZ2dnZfqnPudnZ2d@earthlink.com>
References : 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17
User-Agent : Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.13.0
On 10/2/24 6:32 PM, Lawrence D'Oliveiro wrote:
On Wed, 2 Oct 2024 00:07:15 -0400, 186282@ud0s4.net wrote:
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.
Or, you know, you define a type named “time_t”, which can be specified to
be 32 bits or 64 bits depending on the target architecture build, and use
that type wherever appropriate. Then you don’t have to worry about it any
more.
Ummm ... don't think it's that easy.
Most of the code I've ever writ for dealing with
datetime has lots of vars in each individual
function for doing manipulations/math on datetimes.
They are not 'time_t' but generic 32-bit ints.
Simply creating a 'time_t' ain't gonna fix it.
You'd have to look, see, THINK, about each function
and judge which vars were being used for datetime
stuff, or not.
This sort of thing, and the scale/scope of the issue,
is why I say an "AI" fixer-upper is gonna be needed.
As for the subject line - 'Rust' is as OK as lots
of other languages. Just seems, well, redundant.
Too little Real Stuff gained. Stick to 'C'.