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

Groups > comp.lang.fortran > #73925

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-12 07:36 +0000
Organization news.netcologne.de
Message-ID <tknieo$36gkg$2@newsreader4.netcologne.de> (permalink)
References <tkmbc4$uc0u$1@dont-email.me>

Cross-posted to 3 groups.

Show all headers | View raw

Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
> xkcd: Y2K and 2038
>     https://xkcd.com/2697/
>
> It shouldn't cost more than a trillion dollars or two to investigate this.

The switchover to 64-bit systems should have done this.  Not sure
that this cost a trillion dollars, but computers usually have a
limited lifetime, so they had to be replaced anyway.

Back to comp.lang.fortran | 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 Robin Vowels <robin.vowels@gmail.com> - 2022-11-11 20:31 -0800
  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 FortranFan <parekhvs@gmail.com> - 2022-11-12 06:49 -0800
      Re: xkcd: Y2K and 2038 scott@slp53.sl.home (Scott Lurndal) - 2022-11-12 16:05 +0000
        Re: xkcd: Y2K and 2038 gah4 <gah4@u.washington.edu> - 2022-11-12 10:46 -0800
          Re: xkcd: Y2K and 2038 Thomas Koenig <tkoenig@netcologne.de> - 2022-11-12 19:30 +0000
            Re: xkcd: Y2K and 2038 gah4 <gah4@u.washington.edu> - 2022-11-12 11:56 -0800
              Re: xkcd: Y2K and 2038 Thomas Koenig <tkoenig@netcologne.de> - 2022-11-12 23:45 +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 gah4 <gah4@u.washington.edu> - 2022-11-12 18:08 -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 gah4 <gah4@u.washington.edu> - 2022-11-14 01:54 -0800
            Re: xkcd: Y2K and 2038 Gary Scott <garylscott@sbcglobal.net> - 2022-11-14 09:41 -0600
          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 Robin Vowels <robin.vowels@gmail.com> - 2022-12-02 05:53 -0800
    Re: xkcd: Y2K and 2038 Robin Vowels <robin.vowels@gmail.com> - 2022-11-12 00:02 -0800
    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
    Re: xkcd: Y2K and 2038 Klaus Wacker <klaus.w.wacker@t-online.de> - 2022-11-13 13:23 +0000

csiph-web