While poking around with the source to figure out why some of my disassemblies weren't coming out as expected, I found that there seem to be some useful features in the source that aren't documented.
Mainly, I was very confused that many times, trying to mark a data byte as DEC would result in that byte being interpreted in random different ways which seemed to depend on what the next byte was. Under the hood, it appears that marking as DEC unsets the DATA attribute, so it falls back on trying to auto-interpret it. I found that if I used "+DEC" instead, it would work correctly. What exactly is the "+" meant to do?
Also, these instructions don't appear to be documented:
BREAK - for data bytes, starts printing on a new line, even if it could fit on the previous one.
DWORD - print 32-bit values (I haven't tried it)
While poking around with the source to figure out why some of my disassemblies weren't coming out as expected, I found that there seem to be some useful features in the source that aren't documented.
Mainly, I was very confused that many times, trying to mark a data byte as DEC would result in that byte being interpreted in random different ways which seemed to depend on what the next byte was. Under the hood, it appears that marking as DEC unsets the DATA attribute, so it falls back on trying to auto-interpret it. I found that if I used "+DEC" instead, it would work correctly. What exactly is the "+" meant to do?
Also, these instructions don't appear to be documented:
BREAK - for data bytes, starts printing on a new line, even if it could fit on the previous one.
DWORD - print 32-bit values (I haven't tried it)