| PLEX86 | ||
|
Thou shalt have no other gods before the ANSI C standard 1556
Thou shalt have no other gods before the ANSI C standard 1557 Is this better 1 hoist: proc(n); 0000 HOIST: C07C 0000 .entry 52 52 F7 0006 cvtlw r2,r2 56 52 32 0009 cvtwl r2,r6 52 56 D0 000C movl r6...
I remember that one - I saw it on a lot of calendars when I was a child. Remember typewriters that didn't have a separate '1'? The convention was to use a lower-case L instead. Retraining typists must have been fun. Someone deserves to roast in hell for things like that. Another good one is the vertical bar (), which is easily confused with '1' (or 'I' for that matter). It didn't help that the keyboard on the IBM 029 keypunch put '' right next to '1', where a slightly too long stretch would get the wrong character. Even if you looked at the interpreted card it would be easy to miss the error - especially if the ribbon was worn or one of the print wires was damaged. Unlikely? Perhaps. But I shuddered when I came across an instance of this while converting a mortgage file from one system to a newer one. (The old machine wasn't sophisticated enough to generate a data check.) I went to the customer's microfiche listing and looked closely at the field, and there it was - on file for years without anyone noticing. Thou shalt have no other gods before the ANSI C standard 1558 Perhaps some have taken a more generic path, but I thought the question was fairly specific: Will a C compiler... -- I'm really at ac.dekanfrus if you read it the right way. X Top-posted messages will probably be ignored. See RFC1855. HTML will DEFINITELY be ignored. Join the ASCII ribbon campaign!
|
||||||||
Thou shalt have no other gods before the ANSI C standard 1557 Alt Folklore Computers Newsgroups Thou shalt have no other gods before the ANSI C standard 1555 |
||||||||