Geekzone: technology news, blogs, forums
Guest
Welcome Guest.
You haven't logged in yet. If you don't have an account you can register now.




956 posts

Ultimate Geek
+1 received by user: 222

Trusted
Subscriber

Topic # 127293 5-Aug-2013 16:45
Send private message

Who said it was a once in a lifetime issue.  Apparently the use of 32bit signed integers for dates will bring the world to a halt again (potentially and yes I'm over dramatising my statement).

Y2K bug again

Admittedly if I'm still programming in 25 years it will be a miracle!!




Procrastination eventually pays off.


Create new topic
1524 posts

Uber Geek
+1 received by user: 186


  Reply # 872175 5-Aug-2013 17:06
Send private message

I'll be 71 in 2038, so hopefully it will be someone elses problem!

BDFL - Memuneh
61794 posts

Uber Geek
+1 received by user: 12443

Administrator
Trusted
Geekzone
Lifetime subscriber

 
 
 
 


1524 posts

Uber Geek
+1 received by user: 186


  Reply # 872209 5-Aug-2013 17:46
Send private message

I haven't used my COBOL skills since the 80's, but I hear there is still a big demand for them!



956 posts

Ultimate Geek
+1 received by user: 222

Trusted
Subscriber

  Reply # 872381 5-Aug-2013 21:13
Send private message

Admittedly it's unlikely that any of the systems will still be in operation when this date hits, but I'm sure they said that about the Y2K bug too.




Procrastination eventually pays off.


BDFL - Memuneh
61794 posts

Uber Geek
+1 received by user: 12443

Administrator
Trusted
Geekzone
Lifetime subscriber

  Reply # 872411 5-Aug-2013 22:26
Send private message

The problem is not WHEN the date hits. If you go out now and get a 30 year home loan and your bank is using this kind of systems then it will be hit by it NOW.




651 posts

Ultimate Geek
+1 received by user: 163


  Reply # 872437 5-Aug-2013 23:29
Send private message

Wow. I started to panic. Just done some tests in my native programming language (OpenEdge ABL), luckily I had no problem with dates exceeding the year 2038... phew.







956 posts

Ultimate Geek
+1 received by user: 222

Trusted
Subscriber

  Reply # 872472 6-Aug-2013 08:26
Send private message

jimbob79: Wow. I started to panic. Just done some tests in my native programming language (OpenEdge ABL), luckily I had no problem with dates exceeding the year 2038... phew.

The problem is trying to compare two dates or work out the difference between two dates - if it's more than 1 Billion seconds (around 32 years) then a 32-bit integer will fail.

SAP has a couple of problems already when setting expiry dates that far in the future - their problem isn't 2038 but 2047 as they have a set baseline date!

As Mauricio said a good example will be banks and mortgages where 25+ year calculations are not uncommon!




Procrastination eventually pays off.


3154 posts

Uber Geek
+1 received by user: 965

Trusted
Lifetime subscriber

  Reply # 872533 6-Aug-2013 10:08
Send private message

freitasm: The problem is not WHEN the date hits. If you go out now and get a 30 year home loan and your bank is using this kind of systems then it will be hit by it NOW.

If banks were using systems affected by this problem we would have heard plenty about it 5 years ago. 

BDFL - Memuneh
61794 posts

Uber Geek
+1 received by user: 12443

Administrator
Trusted
Geekzone
Lifetime subscriber

  Reply # 872535 6-Aug-2013 10:10
Send private message

Sure, I don't think NZ banks are affected (as you say we would have heard about it before). But small banks in other countries might not have the same level of expertise we have here...





651 posts

Ultimate Geek
+1 received by user: 163


Reply # 872577 6-Aug-2013 11:30
Send private message

StarBlazer:
jimbob79: Wow. I started to panic. Just done some tests in my native programming language (OpenEdge ABL), luckily I had no problem with dates exceeding the year 2038... phew.

The problem is trying to compare two dates or work out the difference between two dates - if it's more than 1 Billion seconds (around 32 years) then a 32-bit integer will fail.

SAP has a couple of problems already when setting expiry dates that far in the future - their problem isn't 2038 but 2047 as they have a set baseline date!

As Mauricio said a good example will be banks and mortgages where 25+ year calculations are not uncommon!


The Progress software company relealised this potential bug about 9+ years ago and that's why it's inbuilt Advance Business Language (ABL) date interval function returns values as 64bit integer. 





Create new topic



Twitter »

Follow us to receive Twitter updates when new discussions are posted in our forums:



Follow us to receive Twitter updates when news items and blogs are posted in our frontpage:



Follow us to receive Twitter updates when tech item prices are listed in our price comparison site:



Geekzone Live »

Try automatic live updates from Geekzone directly in your browser, without refreshing the page, with Geekzone Live now.


Geekzone Live »

Our community of supporters help make Geekzone possible. Click the button below to join them.

Support Geezone on PressPatron



Are you subscribed to our RSS feed? You can download the latest headlines and summaries from our stories directly to your computer or smartphone by using a feed reader.

Alternatively, you can receive a daily email with Geekzone updates.