AARoads Forum

Meta => Suggestions and Questions => Topic started by: Roadgeekteen on June 03, 2017, 10:49:23 PM

Title: Search.
Post by: 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.
Title: Re: Search.
Post by: Max Rockatansky on June 03, 2017, 11:16:04 PM
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.
Title: Re: Search.
Post by: JJBers on June 03, 2017, 11:26:56 PM
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?
Title: Re: Search.
Post by: 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.
Title: Re: Search.
Post by: 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
Title: Re: Search.
Post by: hotdogPi on June 21, 2017, 10:34:40 AM
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.
Title: Re: Search.
Post by: Scott5114 on June 22, 2017, 01:11:56 PM
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.
Title: Re: Search.
Post by: kkt on June 22, 2017, 05:39:41 PM
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.