Those are part of the display code in the editor screen. The viewer code is runtime generated and not part of this.Mike wrote:tlr wrote:...and for fcbpaint...Code: Select all
nop: 232
Does this include the dynamic code of the display routine? And thus the NOPs are for timing purposes?
I think that the most interesting solution would be just to add an additional statistic table that does not consider the instruction mnemonic only the addressing mode.That's debatable. You'd either have to compare an even longer list of 151 different (documented) opcodes. Or arrange them in a table with '#IMM', 'ZP', 'ZP,X', ..., '(ZP),Y', etc. as table header, with sums for each row and column. In the latter case, most of the table entries would be empty, since the instructions do not cover all combinations. And the statistics as such also gets less reliable, since the numbers get smaller - conversely the programs would need to be bigger to draw good conclusions.I think it would be very interesting to expand our statistics with addressing mode.
OTOH, I'd rather have put, for example, LDA, LDX, LDY into one group. If it were not for the fact that A, X and Y *do not have* equal properties. As it is, the statistics sum up a distinct operation on a register or memory location, regardless in which way the operand was obtained.