Karlos wrote:
They jump to the address + 2, which assuming a byte based offset actually jumps into the immediate word data of the instruction (the #$528B).
Yup.. and $528B is the 'addq.l #1,a3' I mentioned, and makes sense to what the code does (it`s part of a routine that reads a config file and strips all whitespace and comments from each line before parsing with ParseArgs() )
I figured the compare is just a dummy op to save on branching past the addq when it`s first called, otherwise it`d scan from the 2nd char in the line.
It`s something I`ve seen quite a bit lately..poking about inside the OS. Some parts of the OS are riddled with it, others don`t have it at all.
Anyway, ta for confirming my suspicions.