(1 / 1)
Date: September 19, 1989 16:14
From: BERT::ALBAUGH
To: @SYS$MAIL:EE
I have once again stomped a bug which somehow refuses to die. If you are an hardware engineer, please consider including a (maskable) interrupt for "SCOM input empty". See (or write) me for the minimum requirments. Now, if you are a game programmer, _please_ do not attempt to circumvent the carefully designed code in snd_com.asm for "speed" reasons or because "it's too complicated to understand". It's complicated because the ^&$&*^%*&^ job is complicated. In particular, trash any and all old copies of the nefarious "keepcom.c" which keeps popping out of its little corner of code-hell. Any version which does not include the word "reptilian" in it is BAD BAD BAD. The version in [68k_us] is ok. If you come to me with a coin or sound problem, and you are using the old one, I will not only stop working on your problem right then, but I won't come back until somebody of director or higher rank tells me to. I know this sounds petty, but this is at least the third time I've had to deal with this, and posted a note saying "don't do that", and it apparently never penetrates. You might notice I haven't said precisely what is wrong with the non-reptilian keepcom. That's 'cuz I've said it till I was blue in the face and wanted to save it for last and in all caps: DON'T SEND EXCEPTION COMMANDS TO THE 6502 WITHOUT SAYING SO! IF YOU DON'T KNOW WHETHER A COMMAND IS AN EXCEPTIONS, DON'T USE IT! There, I feel a little better Mike
Sep 19, 1989