Rocksolid Light

Welcome to RetroBBS

mail  files  register  newsreader  groups  login

Message-ID:  

I'm a Lisp variable -- bind me!


devel / comp.lang.fortran / Re: xkcd: Y2K and 2038

SubjectAuthor
* xkcd: Y2K and 2038Lynn McGuire
+- Re: xkcd: Y2K and 2038Robin Vowels
+* Re: xkcd: Y2K and 2038Thomas Koenig
|+* Re: xkcd: Y2K and 2038Lynn McGuire
||+- Re: xkcd: Y2K and 2038Thomas Koenig
||+- Re: xkcd: Y2K and 2038Muttley
||+- Re: xkcd: Y2K and 2038David Brown
||+- Re: xkcd: Y2K and 2038FortranFan
||+* Re: xkcd: Y2K and 2038Scott Lurndal
|||`* Re: xkcd: Y2K and 2038gah4
||| `* Re: xkcd: Y2K and 2038Thomas Koenig
|||  `* Re: xkcd: Y2K and 2038gah4
|||   `- Re: xkcd: Y2K and 2038Thomas Koenig
||`* Re: xkcd: Y2K and 2038Keith Thompson
|| +- Re: xkcd: Y2K and 2038gah4
|| +* Re: xkcd: Y2K and 2038red floyd
|| |`- Re: xkcd: Y2K and 2038Kenny McCormack
|| +* Re: xkcd: Y2K and 2038David Brown
|| |+* Re: xkcd: Y2K and 2038gah4
|| ||`- Re: xkcd: Y2K and 2038Gary Scott
|| |`- Re: xkcd: Y2K and 2038Thomas Koenig
|| `- Re: xkcd: Y2K and 2038Klaus Wacker
|+- Re: xkcd: Y2K and 2038Robin Vowels
|+* Re: xkcd: Y2K and 2038Paavo Helde
||`- Re: xkcd: Y2K and 2038Siri Cruise
|`- Re: xkcd: Y2K and 2038Siri Cruise
`* Re: xkcd: Y2K and 2038Klaus Wacker
 `- Re: xkcd: Y2K and 2038Klaus Wacker

Pages:12
Re: xkcd: Y2K and 2038

<jtev7mFoio3U1@mid.individual.net>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=3195&group=comp.lang.fortran#3195

  copy link   Newsgroups: comp.lang.fortran comp.lang.c comp.lang.c++
Followup: comp.lang.fortran
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!news.szaf.org!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: klaus.w.wacker@t-online.de (Klaus Wacker)
Newsgroups: comp.lang.fortran,comp.lang.c,comp.lang.c++
Subject: Re: xkcd: Y2K and 2038
Followup-To: comp.lang.fortran
Date: 14 Nov 2022 13:47:36 GMT
Organization: IEFBR14
Lines: 15
Message-ID: <jtev7mFoio3U1@mid.individual.net>
References: <tkmbc4$uc0u$1@dont-email.me> <tknieo$36gkg$2@newsreader4.netcologne.de> <tknjnl$k9o$1@gioia.aioe.org> <87mt8vlila.fsf@nosuchdomain.example.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Trace: individual.net Sy69CRnbl+Qyxcvhrm01NguzDXBrQXe03YmbA7wtjU+hG1qow5
X-Orig-Path: not-for-mail
Cancel-Lock: sha1:vW7Mz0rYeAOCIbGaIt+zAv97jns=
User-Agent: tin/2.6.2-20220130 ("Convalmore") (Linux/5.15.0-52-generic (x86_64))
 by: Klaus Wacker - Mon, 14 Nov 2022 13:47 UTC

In comp.lang.fortran Keith Thompson <Keith.S.Thompson+u@gmail.com> wrote:
[...]
>
> An unsigned time_t makes it impossible to represent times before 1970.
> Not all software is going to care about that, but in my opinion it's
> an unacceptable price.
>

I read somewhere that the reason for a signed time_t was mainly that
this type was nor just used for time stamps, but also for time
differences.

--
Klaus Wacker klaus.w.wacker@t-online.de
51°29'7"N 7°25'7"E

Re: xkcd: Y2K and 2038

<tkti7i$3acek$1@newsreader4.netcologne.de>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=3196&group=comp.lang.fortran#3196

  copy link   Newsgroups: comp.lang.fortran comp.lang.c comp.lang.c++
Path: i2pn2.org!i2pn.org!weretis.net!feeder8.news.weretis.net!newsreader4.netcologne.de!news.netcologne.de!.POSTED.2001-4dd7-1b20-0-7285-c2ff-fe6c-992d.ipv6dyn.netcologne.de!not-for-mail
From: tkoenig@netcologne.de (Thomas Koenig)
Newsgroups: comp.lang.fortran,comp.lang.c,comp.lang.c++
Subject: Re: xkcd: Y2K and 2038
Date: Mon, 14 Nov 2022 14:09:54 -0000 (UTC)
Organization: news.netcologne.de
Distribution: world
Message-ID: <tkti7i$3acek$1@newsreader4.netcologne.de>
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>
Injection-Date: Mon, 14 Nov 2022 14:09:54 -0000 (UTC)
Injection-Info: newsreader4.netcologne.de; posting-host="2001-4dd7-1b20-0-7285-c2ff-fe6c-992d.ipv6dyn.netcologne.de:2001:4dd7:1b20:0:7285:c2ff:fe6c:992d";
logging-data="3486164"; mail-complaints-to="abuse@netcologne.de"
User-Agent: slrn/1.0.3 (Linux)
 by: Thomas Koenig - Mon, 14 Nov 2022 14:09 UTC

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.

Re: xkcd: Y2K and 2038

<tktnji$1phlq$1@dont-email.me>

  copy mid

https://www.rocksolidbbs.com/devel/article-flat.php?id=3198&group=comp.lang.fortran#3198

  copy link   Newsgroups: comp.lang.fortran
Path: i2pn2.org!i2pn.org!eternal-september.org!reader01.eternal-september.org!.POSTED!not-for-mail
From: garylscott@sbcglobal.net (Gary Scott)
Newsgroups: comp.lang.fortran
Subject: Re: xkcd: Y2K and 2038
Date: Mon, 14 Nov 2022 09:41:37 -0600
Organization: A noiseless patient Spider
Lines: 22
Message-ID: <tktnji$1phlq$1@dont-email.me>
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>
<2945e197-a0f0-4fbd-a9fa-5b95059e8b97n@googlegroups.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Injection-Date: Mon, 14 Nov 2022 15:41:38 -0000 (UTC)
Injection-Info: reader01.eternal-september.org; posting-host="1d15b288af9be0837a334eeb414a1ed2";
logging-data="1885882"; mail-complaints-to="abuse@eternal-september.org"; posting-account="U2FsdGVkX1/OeadBoub3IgUq+NVL/3Q9roN4jVtWfdU="
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101
Thunderbird/102.4.2
Cancel-Lock: sha1:28VK84QDyfUlnF5+WcVgSMvqmkQ=
Content-Language: en-US
In-Reply-To: <2945e197-a0f0-4fbd-a9fa-5b95059e8b97n@googlegroups.com>
 by: Gary Scott - Mon, 14 Nov 2022 15:41 UTC

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.

Pages:12
server_pubkey.txt

rocksolid light 0.9.81
clearnet tor