2016 Bug Hits Text Messages, Payment Processing
An anonymous reader writes "It seems some systems are suffering from a Y2K16 bug. When 2009 ticked over to 2010, some Australian EFTPOS machines skipped to the year 2016. Coincidentally, some Windows Mobile users are also having issues with their new year SMSes coming from 2016. What function could cause this kind of error?"
Uh? No, traditionally appending a 0x denotes that the value is in hexadecimal. Ask any C programmer.
XML is like violence. If it doesn't solve the problem, use more.