Blown To Bits

Y2010?

Sunday, January 3rd, 2010 by Harry Lewis
Organ generic generic sale information recipients who develop donor-derived hepatitis C can most likely clear buy generic zyprexa the infection with antiviral treatments. Doctors may consider a combined find cheap viagra online heart and liver transplant for people with severe liver damage augmentin no prescription resulting in liver failure. After approval for heart transplant surgery, order flovent no prescription a person will join the United Network for Organ Sharing celexa for sale list. Some of these medications can have serious side effects, colchicine online without prescription so a doctor needs to find those that work best buy viagra from canada for the individual. Recent studies show that people who receive cheap cialis from usa heart donations from those who had hepatitis C achieve survival estrace us rates similar to those who received hearts from people without quinine hepatitis C. Part C plans can also include a drug buy clomid from canada coverage known as Part D, which covers prescription drugs only. no prescription for The remaining part of the liver in the donor and buy bentyl from canada the section of liver in the person receiving the transplant cheap lipitor grow back to normal size after surgery. Artificial liver support systems.

The problems that were widely feared fro the year 2000 — computers failing to add 1 to 1999 correctly because they had been coded to use only two digits for the “year” field — have actually occurred, 10 years late. There have been two reports of software thinking the day after December 31, 2009 is January 1, 2016.

Some phones are showing 2016 dates on received text messages.

And some retail computer terminals are making the same mistake, causing them to reject customer credit cards with expiration dates prior to 2016.

What’s up? There is some speculation on Slashdot that (a) only the last two digits are being stored (“10” instead of “2010”), and then (b) the “10” is somehow being interpreted as hexadecimal rather than decimal (which would make it decimal 16).

Nothing is truly hard to imagine in the hearts and minds of a corner-cutting coder, but (a), in this day of cheap memory and with the Y2K problem still in our rear view mirrors, would be really dumb, and (b) requires imagining a really perverse data representation (encoding the decimal digits in successive 4-bit “nibbles”, and then forgetting that you’d done that and interpreting the fully 8-bit byte as a binary number).

Comments are closed.