If you're still using a 32bit version of anything then, I'll be slightly worried :)
On 29/08/2010, at 9:25 AM, Olwen Williams wrote: > I just came accross the Y2K38 bug in a hint in a group mailing from a > recruiting firm. > In 2038 your code could fail > It's something to be aware of. You need to furture proof your code. > http://www.sitepoint.com/blogs/2010/08/24/is-your-php-application-affected-by-the-y2k38-bug/ > > The COBOL developers of the 1970's (I was there) never thought 2000 would > come. Some of my colleagues from that time made good money by being > available on 31/12/1999. > I was a PICK developer in the 1980's. Dates were stored as days after > 31/12/69. This gave rise to a day 10000 issue (18th May 1997). Even a year > before that date I found developers ignoring it. I worked for one firm who > went broke. I advised one of their customers I'd been supporting to replace > their payroll system before that date -- but come May 18 I got a phone call > (HELP!!!!) > > -- > NZ PHP Users Group: http://groups.google.com/group/nzphpug > To post, send email to [email protected] > To unsubscribe, send email to > [email protected] --- Simon Welsh Admin of http://simon.geek.nz/ Who said Microsoft never created a bug-free program? The blue screen never, ever crashes! http://www.thinkgeek.com/brain/gimme.cgi?wid=81d520e5e -- NZ PHP Users Group: http://groups.google.com/group/nzphpug To post, send email to [email protected] To unsubscribe, send email to [email protected]
