2 ms·
Only if you'd been raised on Java. There had been the shift from 16->32 bit not long before that, so it's not that much of a stretch, and 8->16 before that (we
by zwischenzug 15y ago
Only if you'd been raised on Java.
There had been the shift from 16->32 bit not long before that, so it's not that much of a stretch, and 8->16 before that (well after I got my first computer).
We found an almost identical bit-mismatch bug in a programming language that led a bitmap of tcp connections to appear to go crazy on a customer install in a core piece of software. These bugs cost.
- tsotha 15y agoYeah, in that time period you couldn't really get away from writing really defensively. It was even worse, earlier. When I wrote C code for x86 there were all sorts of different memory models you could choose from at compilation, and we were producing both a 16 bit and a 32 bit (for the daring) versions of our product. You couldn't assume anything. I write java now and this is not something I miss.