Forums before death by AOL, social media and spammers... "We can't have nice things"
|    alt.os.development    |    Operating system development chatter    |    4,255 messages    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
|    Message 2,338 of 4,255    |
|    mutazilah@gmail.com to Rod Pemberton    |
|    Re: Year 2030 problem    |
|    19 Jun 21 21:42:51    |
      From: muta...@gmail.com              On Sunday, June 20, 2021 at 2:24:48 PM UTC+10, Rod Pemberton wrote:              > > I was just planning on dynamically shifting that 1970.       > >       > It'd work on the software side, but you'd have the       > side effect of dates and times being off every decade.              time_t is only supposed to be for internal use. You can't       rely on it being anything in particular.              > Why wouldn't you use a larger period like the nearly       > seventy years from 1970 to 2038?              That's what I was originally thinking of doing, but I       "realized" that that would mean when I did a "dir"       all of my data would appear to be between 2038       and 2100+.              > I don't remember enough about the CMOS RTC to know       > if it's an issue.              It doesn't matter if the RTC covers the year 0000 to 9999.       I have a 32-bit limit, so I need a scheme to work within that.              BFN. Paul.              --- SoupGate-Win32 v1.05        * Origin: you cannot sedate... all the things you hate (1:229/2)    |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca