Currently, gb-opcodes can be rendered with octal numbers, example: https://gbdev.io/gb-opcodes/optables/darkoctal
I like the idea of an 8 column mode, but not the idea of using octal numbers, since it's otherwise never used as a number base for representing GB opcodes.
Suggested solution: Offer an 8 column mode, but denote the opcodes as hexadecimal numbers. For example denote the column headers for example as $0x/$8x, $1x/$9x, $2x/$Ax, etc. For example denote the row headers $00..., $08... $10..., $18... This would produce the benefits of an 8 column mode without needing octal numbers.
Currently, gb-opcodes can be rendered with octal numbers, example: https://gbdev.io/gb-opcodes/optables/darkoctal
I like the idea of an 8 column mode, but not the idea of using octal numbers, since it's otherwise never used as a number base for representing GB opcodes.
Suggested solution: Offer an 8 column mode, but denote the opcodes as hexadecimal numbers. For example denote the column headers for example as $0x/$8x, $1x/$9x, $2x/$Ax, etc. For example denote the row headers $00..., $08... $10..., $18... This would produce the benefits of an 8 column mode without needing octal numbers.