Blown To Bits

Y2010?

Sunday, January 3rd, 2010 by Harry Lewis
It amikacin overnight is important for people to always follow the instructions provided buy levitra without prescription on the product label or as directed by a doctor. buy cheap gel internet Environmental factors, such as bright lights, loud noises, strong odors, canadian ventolin and weather changes, can trigger migraine headaches. When a typical tablet viagra bladder needs to empty, the brain signals the detrusor muscle serevent without prescription to contract and the urethral sphincter to relax, allowing the buy cheap aldactone person to urinate. Also, there will often be more signs buy cheap accutane without prescription once there is both back pain and constipation, such as cialis price weight loss, night sweats, and fatigue. Treatment and physical and find pamoate no prescription required occupational therapy can help improve muscle tone for many people buying cheap glyburide side effects canada with hypotonia. For both children and adults, the most important cipro price part of treatment is keeping fluids up by drinking juice, purchase cheapest accutane no prescription tablets sports drinks, or other noncaffeinated liquids. Some skin abscesses will resolve.

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.