Re: Y2K38 bug (January 19, 2038)

In article <b2321bbf-e9a1-40d5-9261-db53a98a8dadn@googlegroups.com>,
J Naman  <jnaman2@gmail.com> wrote:

Is there any plan or schedule for POSIX to replace the Unix 32-bit time by a
64-bit time format to avoid the Y2K38 bug ( January 19, 2038, at 03:14:07 UTC.)?
I am really asking if GNU awk or other awks expect to upgrade before or after the
next revision of POSIX in 2026? Is there any certainty that POSIX WILL revise
time in 2026? I keep running into Y2K38 issues with some US government data. mktime() is no big
deal to handle at the user level, but strftime() IS a (the) real problem.

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.
--
It's possible that leasing office space to a Starbucks is a greater liability
in today's GOP than is hitting your mother on the head with a hammer.