CompuServe Messages

That isn't the type of thing I'm describing. What I'm refering to is two completely seperate and independent routines with no common code that are "woven" together so that the bytes making up the opcodes for one routine are the data bytes for the second. The bytes making up the second routines opcodes are the first routines data bytes. Something like this: r1 lda #$a9 ; entry for first routine nop r2 equ r1 + 1 ; entry for second routine If this is routine is run at r1 on exit a is $a9. If run at r2 (the $a9 data byte for the lda) a is a $ea on exit. The routine I was talking about used this technique to hook one of the game routines to one of the cp routines. The total size was something like 1K. What a mess.