writing a bunch of completely untested 6502 assembly using my own hand-rolled 6502 assembler because I don't have enough of a skeleton to actually run any of it and I don't feel like writing one right now
surely there's no way this will go awry
The Apple II machine language monitor is kind of a miracle... I can't think of another 8-bit home computer that had an assembler, disassembler, and debugger built-in to ROM. An indispensable tool for this project.
As a kid I just knew it as the cryptic unusable thing that showed up when my pirated games crashed.
@SpindleyQ this sounds like a job for a test suite.
and getting that dev loop time down- maybe, so that the one line of code that breaks everything is the one you just wrote
@zensaiyuki I also really need to write a lot more introspection tools - the disassembler built-in to the Apple II is very nice but it doesn't help debug codegen failures with bytecode for the VM I implemented
@SpindleyQ the amstrad CPC video memory layout is similarly cursed, pixel rows aren't contiguous in memory, each contiguous row of pixel data is actually 8 pixels further down on the screen. it has to do with how the display chip accesses memory apparently, and amstrad being amstrad (make it work, but make it work cheap)
I hear it's even worse on the BBC micro (which used the same video generation chip)
@SpindleyQ if you want a more in-depth explanation:
Server run by the main developers of the project It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!