@typhlosion there's seriously no "branch when the zero flag is set"??
@Fuego i, uh,
[runs away]
@typhlosion *still yelling* HOW DO YOU CHECK FOR GTE AND LT??! WHAT ALU FLAGS DO YOU EVEN SUPPORT?
@Fuego pls ;-;
@typhlosion shhh shhh *cuddles* it'll be okay... *pets you gently* *holds you tightly* *whispers* seriously though, what flags are in your flags register...
@Fuego i don't have a flags register - it's based vaguely on MIPS, which also doesn't have a flags register
@typhlosion ok but like the mips ALU still passes you back at least carry, overflow, and zero... its okay. It was a hobby. And you're cute. So I wont do anything hasty.
@Fuego i mean the jump opcode still has plenty of opcodes paired with it that are as yet invalid; i could stuff a jez in there
@Fuego i mean. sub-opcodes.
@Fuego okay what i really mean is that the first hexit of an (always 16-bit) instruction is the opcode; some instructions treat the last hexit as a sub-opcode so i can get more instructions in there that only need two register parameters or such
@typhlosion is this on github?
@typhlosion haha you're more principled than I am ;)
@Fuego well it's basically just that i don't want to put my terrible code into the public and open it to unsolicited feedback until it has at least passed some modicum of quality control