Re: xkcd: Y2K and 2038

From	Gary Scott <garylscott@sbcglobal.net>
Newsgroups	comp.lang.fortran
Subject	Re: xkcd: Y2K and 2038
Date	2022-11-14 09:41 -0600
Organization	A noiseless patient Spider
Message-ID	<tktnji$1phlq$1@dont-email.me> (permalink)
References	(1 earlier) <tknieo$36gkg$2@newsreader4.netcologne.de> <tknjnl$k9o$1@gioia.aioe.org> <87mt8vlila.fsf@nosuchdomain.example.com> <tkt0kg$1nldh$1@dont-email.me> <2945e197-a0f0-4fbd-a9fa-5b95059e8b97n@googlegroups.com>

Show all headers | View raw

On 11/14/2022 3:54 AM, gah4 wrote:
> On Monday, November 14, 2022 at 1:09:40 AM UTC-8, David Brown wrote:
> 
> (snip)
> 
>> Small embedded systems which also track the date will generally not do
>> so using Unix epoch timestamps - it's a lot easier to hold a structure
>> with second, minute, hour, day, month, year fields and update it. That
>> avoids all the mess of locales and time and date conversions.
> 
> Reminds me that I have a sprinkler timer that you program with the year.
> It needs the year because you can set it to water on even or odd days,
> and so has to get leap years right.
> 
> But if it watered on the wrong day, it wouldn't be the worst thing.

Unless code enforcement catches you watering on the wrong day ... :(

> 
> You can program it by week days, then it doesn't even need the month,
> but you still have to set year and month.

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