Change continue to use exact addresses
Using > is not very helpful when trying to break in a subroutine that gets jumped across often.
I've personally patched the assembler I use to output label addresses so I know where to continue to.
return False when nothing matches.
ignore blank and only-commented lines.
test that mostly-blank lines get ignore.
implemented long and short literals
tests for short and long literals.
make it so the register thing only matches one-length strings end.
implemented parsing opcodes.
Doesn't quite work yet, because of a conflict with the register names.
Gimme a second.
tests for parsing all the opcodes.
actually I don't need next word literals. other things will handle that
parse next word literals
test parse next word pointers.
parse next word pointers.
implemented and tested parsing SP, PC, and O
implemented POP PEEK and PUSH, and tested them.
made it so value parsers return their code and None or their next word.
test parsing register pointers
beginnings of parser tests and tests for parsing registers
what I have so far re: parsers.
A metaclass, a decorator, a base class, and the real thing.
describe `continue` in the readme.
implemented `continue_until` in the debugger.
explain dumprange/dr in the readme
dump_range command in the debugger.
fixed a docstring and a newline.
more clean up.
fixed an id conflict by moving sixteen.values sixteen.boxes, moved a
bunch of stuff around, and renamed IF_X to IFX
cleaned things up in DCPU16, moved a lot to the class scope.
mention the disassembler in the readme.
a simple disassembler.
split DCPU16.cycle in parse_instruction and cycle.
use file_to_ram in sixteen-debug.