When working with a memory dump, sections of assembly code are often interspersed with long sections of data inbetween. A command to jump to the next or previous Code Start Point or Code Stop Point, would be useful to quickly jump over data sections to the next section of code.
I guess it could work something like this:
- If the current line is long comment, or is a statement with an opcode that isn't a 6502 opcode (e.g.
.dd11, .str`, etc.) find and jump to the next line that has a 6502 opcode.
- If the current line is statement with a 6502 opcode, jump to the next line that isn't a 6502 opcode.
Other possible approaches:
- Look at whether a line has Flags or not (code has flags, while data and comments don't)
- Look for blank lines: I notice SourceGen adds blank lines around sections of code. Perhaps a 'Navigate to next/previous blank line' commands might be simple and sufficient enough to be useful.
When working with a memory dump, sections of assembly code are often interspersed with long sections of data inbetween. A command to jump to the next or previous Code Start Point or Code Stop Point, would be useful to quickly jump over data sections to the next section of code.
I guess it could work something like this:
.dd11,.str`, etc.) find and jump to the next line that has a 6502 opcode.Other possible approaches: