Take the 2-minute tour ×  I know that a lot of Y2K efforts/scare
was somehow centered on COBOL, deservedly or not. (heck, I saw
minor Y2K bug in a Perl scripts that broke 1/1/2000)  What I'm
interested in, was there something specific to COBOL as a
language which made it susceptible to Y2K issues?  That is, as
opposed to merely the age of most programs written in it and
subsequent need to skimp on memory/disk usage driven by old
hardware and the fact that nobody anticipated those programs to
survive for 30 years?  I'm perfectly happy if the answer is
"nothing specific to COBOL other than age" - merely curious,
knowing nothing about COBOL.  share|improve this question If we
learned anything from the Y2K bug, it's that we need to look
forward and keep in mind the 2038 bug :)
en.wikipedia.org/wiki/Year_2038_problem –  Mark Rushakoff Sep 23
'09 at 1:03 Or the Y1C problem
(en.wikipedia.org/wiki/Y1C_Problem) :D –  RCIX Jan 2 '10 at
11:25 add comment  10 Answers  up vote 4 down vote accepted  Yes
and No. In COBOL yo