Sujet : Re: Y2K38 bug (January 19, 2038)
De : toylet.toylet (at) *nospam* gmail.com (Mr. Man-wai Chang)
Groupes : comp.lang.awkDate : 11. Mar 2024, 12:33:54
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <usmq73$3j5ib$2@toylet.eternal-september.org>
References : 1 2
User-Agent : Mozilla Thunderbird
On 9/3/2024 4:11 am, Kenny McCormack wrote:
This is a non-issue in GAWK. Note that AWK in general does not have an
integer type. It just has a "number" type - and that type is a C double.
Observe:
% gawk 'BEGIN { print strftime("%c",1e12)}'
Thu Sep 26 19:46:40 33658
%
So, I think we're good.
Well, you can always outsource the job using system()! :)
Year 2038 problem is not just a software issue. You also need 64-bit CPU to compute dates. Awk is just a tool that makes use of operating systems.
Year 2038 problem - Wikipedia
<
https://en.wikipedia.org/wiki/Year_2038_problem>
Re: Y2K38 bug (January 19, 2038)
Re: Y2K38 bug (January 19, 2038)