News:

Thank you for your patience during the Forum downtime while we upgraded the software. Welcome back and see this thread for some new features and other changes to the forum.

Main Menu

Search.

Started by Roadgeekteen, June 03, 2017, 10:49:23 PM

Previous topic - Next topic

Roadgeekteen

I found this out when searching the SMF thing. In 27.3 years, the search function will become obsolete because of limits. Will the mods try to do anything about this is 27.3 years? Just a fun fact I wanted to share with you guys.
God-emperor of Alanland, king of all the goats and goat-like creatures

Current Interstate map I am making:

https://www.google.com/maps/d/u/0/edit?hl=en&mid=1PEDVyNb1skhnkPkgXi8JMaaudM2zI-Y&ll=29.05778059819179%2C-82.48856825&z=5


Max Rockatansky

Its probably a pretty optimistic assumption that this site will even be here 27.3 years from now.  I'm sure it could be patched out a lot like how the supposed disaster Y2K was "going" to be.

JJBers

Quote from: Roadgeekteen on June 03, 2017, 10:49:23 PM
I found this out when searching the SMF thing. In 27.3 years, the search function will become obsolete because of limits. Will the mods try to do anything about this is 27.3 years? Just a fun fact I wanted to share with you guys.
Wait how? What limits?
*for Connecticut
Clinched Stats,
Flickr,
(2di:I-24, I-76, I-80, I-84, I-95 [ME-GA], I-91)

Scott5114

I assume it has something to do with the year 2038 problem, but if we're still using signed 32-bit integers for our dates by then, I will mail a postcard to Alex with the single word "why" written on it.
uncontrollable freak sardine salad chef

hbelkins

Quote from: Scott5114 on June 20, 2017, 06:17:23 PM
I assume it has something to do with the year 2038 problem, but if we're still using signed 32-bit integers for our dates by then, I will mail a postcard to Alex with the single word "why" written on it.

There's a Year 2038 problem? If there really is, maybe those people in the federal government who are still working on the Y2K issue should refocus. :-p


Government would be tolerable if not for politicians and bureaucrats.

hotdogPi

2017+27.3≠2038, no matter how you round.

Anyway, the reason why 2038 could be a problem is because the standard is to use the number of seconds starting from 1970, which will reach 2^31 in 2038.
Clinched, minus I-93 (I'm missing a few miles and my file is incorrect)

Traveled, plus US 13, 44, and 50, and several state routes

I will be in Burlington VT for the eclipse.

Scott5114

Quote from: hbelkins on June 21, 2017, 10:31:56 AM
Quote from: Scott5114 on June 20, 2017, 06:17:23 PM
I assume it has something to do with the year 2038 problem, but if we're still using signed 32-bit integers for our dates by then, I will mail a postcard to Alex with the single word "why" written on it.

There's a Year 2038 problem? If there really is, maybe those people in the federal government who are still working on the Y2K issue should refocus. :-p

It's not a huge problem, or at least not one that is difficult to solve. Time is stored as the number of seconds since January 1, 1970, and in 2038 that number will exceed the limits of a 32-bit variable. Switching to a 64-bit variable fixes the problem for several million years.

Most computers in use today use a 64-bit architecture, and it seems unlikely that there will be too many unpatched 32-bit applications in use in 21 years.

I have no idea what the OP was referring to in 27.3 years.
uncontrollable freak sardine salad chef

kkt

Quote from: Scott5114 on June 20, 2017, 06:17:23 PM
I assume it has something to do with the year 2038 problem, but if we're still using signed 32-bit integers for our dates by then, I will mail a postcard to Alex with the single word "why" written on it.

yes, dates are 64 bit data in most applications already.



Opinions expressed here on belong solely to the poster and do not represent or reflect the opinions or beliefs of AARoads, its creators and/or associates.