Re: Two new PRGs
Date: 1998-02-16 21:50:43

Hallo Andre,

> Can you add comments to your disassembly with this file too?

No, but I've given it a thought. The problem is: what kind of comment must the 
disassembler put where? Replacing $FFAE with UNLISTEN is enough comment for me 
and other (even a little bit) experienced programmers, in this case I don't 
need a line to tell me what the routine UNLISTEN does. 75% of all comment is 
ment for only one particular occasion:
Part of the FAC = FAC * 10 routine...
    tax         ; FAC = 0 ?
    beq $BAF8   ; yes -> ready
    adc #2      ; exponent + 2 is equal * 4

I don't think you'll find this kind of comment twice so what is the point of 
automating it?

Another thing is that in this case known software = listing on paper is used. 
What about unknown software? What kind of comment can you add in that case?

The above does not mean that I reject the idea but until somebody can convince 
me to use it, I won't implement it (unless especially requested) The idea was 
already there:

COMA $1234 ; xxxx    means: place comment '; xxxx' at address $1234
COMJ $FFAE ; xxxx    means: place comment '; xxxx' where branch, subroutine or 
jump to address $FFAE is used

> > The ASTERIX command means to translate all addresses since last label as 
> "label + x":
> This is something recomment does not. 

I implemented that last weekend, did not need it befor :-) 

Until now I haven't implemented macros in my assembler. The main reason is as 
told above, I don't use them. But the second reason is more painfull for me: I 
haven't found a nice way to program it. The big problem is where to store them 
after you have found them in your sourcecode. I could store them as sepperate 
files or I could store the linenumber where they were found but both solutions 
mean a lot of I/O = time. Storing them in RAM is a solution but I also have 
some problems there.... Solutions, ideas, even critics are welcome.

Groetjes, Ruud

Archive generated by hypermail 2.1.1.