Changes

Jump to navigation Jump to search
1 byte removed ,  20:57, April 22, 2016
better caption
Line 1: Line 1: −
[[File:Bug de l'an 2000.jpg|thumb|right|Computerized display sign that in the year 2000 with Y2K bug.]]The '''Y2K problem''' is a problem in [[computer]] [[hardware]] and [[software]] [[programming]] where unintended results may take place if a year represented as two digits is not interpreted correctly.  There are two basic aspects to the Y2K problem:<br />  - Determining the correct value of a 2-digit year.  ''Example - does "20" represent 1920 or 2020?''<br />  - Performing date-based calculations correctly.  ''Example - if you subtract "97" (1997) from "07" (2007), will you get 10 years, or minus 90?''
+
[[File:Bug de l'an 2000.jpg|thumb|right|Computerized display sign that shows Y2K bug on Jan 3, 2000.]]The '''Y2K problem''' is a problem in [[computer]] [[hardware]] and [[software]] [[programming]] where unintended results may take place if a year represented as two digits is not interpreted correctly.  There are two basic aspects to the Y2K problem:<br />  - Determining the correct value of a 2-digit year.  ''Example - does "20" represent 1920 or 2020?''<br />  - Performing date-based calculations correctly.  ''Example - if you subtract "97" (1997) from "07" (2007), will you get 10 years, or minus 90?''
    
The origins of the problem lie in the high cost of data storage in the early days of computing, where  storing a date in 6 digits (mmddyy) versus 8 (mmddyyyy) could result in significant savings depending on volume.  If the specifications for a piece of software were well-designed this is not a problem, but in many cases the century component of a 2-digit year was assumed instead of being explicitly accounted for in programming.
 
The origins of the problem lie in the high cost of data storage in the early days of computing, where  storing a date in 6 digits (mmddyy) versus 8 (mmddyyyy) could result in significant savings depending on volume.  If the specifications for a piece of software were well-designed this is not a problem, but in many cases the century component of a 2-digit year was assumed instead of being explicitly accounted for in programming.
SkipCaptcha
3,995

edits

Navigation menu