John ffitch wrote:

> Can anyone see a reason for keeping this opcode 
> in the system?  It appears to be a noop and is 
> not in the Alternative Manual.

I'd like to point out that I use the files entry1.c and entry2.c to
determine which opcodes to include. The soundouts entry was commented
out in the entry1.c file so that's why it isn't in the manual.

BTW, I hope the new every-opcode-as-a-plugin scheme is as easy to
follow as the entry*.c files. Are they all going to be in the same
sub-directory?  Is there going to be a standard, consistent layout for
opcodes?


=====
-- 
kwconder at yahoo dot com

__________________________________
Do you Yahoo!?
Yahoo! Finance: Get your refund fast by filing online.
http://taxes.yahoo.com/filing.html