| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Re: `Leap Second` to Be Added on New Year`s Eve This Year |
Subject: Re: 'Leap Second' to Be Added on New Year's Eve This Year @Newsgroups: comp.lang.c,comp.programming,alt.comp.os.windows-10,alt.os.linux.˙ @ ubuntu @References: @ @ @ @ From: Mark Lloyd @User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 @ Thunderbird/45.5.1 @MIME-Version: 1.0 @In-Reply-To: @Lines: 40 @Message-ID: @X-Complaints-To: abuse(at)newshosting.com @NNTP-Posting-Date: Sat, 31 Dec 2016 20:34:06 UTC @Organization: Newshosting.com - Highest quality at a great price! www.newshos˙ @ ting.com @Date: Sat, 31 Dec 2016 14:34:05 -0600 @X-Received-Bytes: 2528 @X-Received-Body-CRC: 1574873826 @Content-Type: text/plain; charset=windows-1252; format=flowed @Content-Transfer-Encoding: 7bit @Xref: b4gate.uuhec.net comp.lang.c:41978 comp.programming:1414 alt.comp.os.wi˙ @ ndows-10:1786 On 12/30/2016 07:48 PM, Keith Thompson wrote: > Mark Lloyd writes: >> On 12/30/2016 04:37 PM, Keith Thompson wrote: >> >> [snip] >> >>> The time is stored in a time_t value returned by the time() >>> function. The time_t type is required to be a real type (integer >>> or floating-point, not complex) capable of representing times. >>> (On many systems it's a signed integer representing seconds since >>> 1970-01-01 00:00:00 UTC.) >> >> Used to be 32-bit, why I thought Y2K was going to be much less of a >> problem than Y2.038K (Jan 17 2038 IIRC). > [...] > > Tue 2038-01-19 03:14:08 UTC I knew it was around that time, from having to deal with that when my website was on a 32-bit server. IIRC the negative limit is in December 1901. > 64-bit systems already use a 64-bit signed integer for time_t, which > postpones the problem for about 292 billion years. And since C requires > long long to be at least 64 bits, I expect that 32-bit systems (and > smaller ones, if any) will transition to 64-bit time_t before 2038. 2^63 = 9.22337203685e+18 seconds, or 292,277,024,627 years (assuming leap year rules don't change). > Unlike 2-digit years, I suspect that most stored time_t values (which > are rarely displayed) are in files that can be converted reasonably > easily. > -- Mark Lloyd http://notstupid.us/ "Call on God, but row away from the rocks." [Indian proverb] --- ViaMAIL!/WC v2.00* Origin: ViaMAIL! - Lightning Fast Mailer for Wildcat! (1:261/20) SEEN-BY: 34/999 90/1 116/18 120/302 123/500 128/187 140/1 218/700 222/2 SEEN-BY: 230/150 240/1120 249/303 250/1 261/38 100 266/404 267/155 280/464 SEEN-BY: 280/1027 282/1031 1056 292/907 908 320/119 219 340/400 393/68 396/45 SEEN-BY: 633/267 280 640/384 712/620 848 770/1 801/161 189 2320/100 105 @PATH: 261/20 116/18 261/38 712/848 633/267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.