Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.lang.c++ > #87374

Re: xkcd: Y2K and 2038

From Thomas Koenig <tkoenig@netcologne.de>
Newsgroups comp.lang.fortran, comp.lang.c, comp.lang.c++
Subject Re: xkcd: Y2K and 2038
Date 2022-11-14 14:09 +0000
Organization news.netcologne.de
Message-ID <tkti7i$3acek$1@newsreader4.netcologne.de> (permalink)
References <tkmbc4$uc0u$1@dont-email.me> <tknieo$36gkg$2@newsreader4.netcologne.de> <tknjnl$k9o$1@gioia.aioe.org> <87mt8vlila.fsf@nosuchdomain.example.com> <tkt0kg$1nldh$1@dont-email.me>

Cross-posted to 3 groups.

Show all headers | View raw

David Brown <david.brown@hesbynett.no> schrieb:
> On 13/11/2022 03:00, Keith Thompson wrote:

>> But since C and C++ require support for 64-bit integers anyway, it
>> should be practical to require 64-bit time_t even on 32-bit systems.
>
> Yes.
>
>> (Not sure about Fortran.)
>
> (That's better than me - I haven't a clue about Fortran!)

Fortran has the DATE_AND_TIME inrinsic, which returns the the date
and time in calendar format, either as YYYYMMDD and HHMMSS.SSS and
[+/-] HHMM for the zoneif you chose character arguments, or as an
array of integer with the same info.

The library is supposed to take care of how to get the value
from the operating system, user programs need not bother.

There are also non-standard extensions which mimic system
behavior, but those should be avoided, at least in new code.

Back to comp.lang.c++ | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

xkcd: Y2K and 2038 Lynn McGuire <lynnmcguire5@gmail.com> - 2022-11-11 14:29 -0600
  Re: xkcd: Y2K and 2038 Thomas Koenig <tkoenig@netcologne.de> - 2022-11-12 07:36 +0000
    Re: xkcd: Y2K and 2038 Lynn McGuire <lynnmcguire5@gmail.com> - 2022-11-12 01:58 -0600
      Re: xkcd: Y2K and 2038 Thomas Koenig <tkoenig@netcologne.de> - 2022-11-12 08:30 +0000
      Re: xkcd: Y2K and 2038 Muttley@dastardlyhq.com - 2022-11-12 10:00 +0000
      Re: xkcd: Y2K and 2038 David Brown <david.brown@hesbynett.no> - 2022-11-12 11:29 +0100
        Re: xkcd: Y2K and 2038 Bart <bc@freeuk.com> - 2022-11-12 11:03 +0000
          Re: xkcd: Y2K and 2038 David Brown <david.brown@hesbynett.no> - 2022-11-12 12:57 +0100
            Re: xkcd: Y2K and 2038 Bart <bc@freeuk.com> - 2022-11-12 15:56 +0000
        Re: xkcd: Y2K and 2038 Michael S <already5chosen@yahoo.com> - 2022-11-12 10:05 -0800
      Re: xkcd: Y2K and 2038 scott@slp53.sl.home (Scott Lurndal) - 2022-11-12 16:05 +0000
      Re: xkcd: Y2K and 2038 Keith Thompson <Keith.S.Thompson+u@gmail.com> - 2022-11-12 18:00 -0800
        Re: xkcd: Y2K and 2038 red floyd <no.spam.here@its.invalid> - 2022-11-13 09:49 -0800
          Re: xkcd: Y2K and 2038 gazelle@shell.xmission.com (Kenny McCormack) - 2022-11-14 09:14 +0000
        Re: xkcd: Y2K and 2038 David Brown <david.brown@hesbynett.no> - 2022-11-14 10:09 +0100
          Re: xkcd: Y2K and 2038 Thomas Koenig <tkoenig@netcologne.de> - 2022-11-14 14:09 +0000
        Re: xkcd: Y2K and 2038 Klaus Wacker <klaus.w.wacker@t-online.de> - 2022-11-14 13:47 +0000
    Re: xkcd: Y2K and 2038 Paavo Helde <eesnimi@osa.pri.ee> - 2022-11-12 16:13 +0200
      Re: xkcd: Y2K and 2038 Siri Cruise <chine.bleu@yahoo.com> - 2022-11-12 15:49 -0700
    Re: xkcd: Y2K and 2038 Siri Cruise <chine.bleu@yahoo.com> - 2022-11-12 15:47 -0700
  Re: xkcd: Y2K and 2038 Klaus Wacker <klaus.w.wacker@t-online.de> - 2022-11-13 12:45 +0000

csiph-web