> > 1) 6502 disassembly: op6502 in 6502dasm.c contains a lot of opcodes not supported > by > > a 6502 CPU. Does it make sense to submit a "fixed" op6502 or is someone using it in > > current form? If so, I could add a basic_op6502 and switch between the current form > > and the basic form with a menu choice like "Basic Opcodes". > > I believe that function is also used by other 6502 family members (especially in > MESS), so removing the extra opcodes is a non-starter.
I think there are collisions between undocumented opcodes and other 6502 chips with extra documented instructions. So if the disassembler is shared then it shouldn't be, or it should at least switch itself.
smf
|