Monitor Program Critique Wanted!

[BigDumbDinosaur]

JimBoyd wrote:

A jump table is a way to future proof your design.

Probably the best-known use of a jump table is in the Commodore “kernal,” which every eight-bit Commodore machine has had.

[Sean]

Absent a software interrupt capability, it seems a good approach. Are there others?

BigDumbDinosaur wrote:

JimBoyd wrote:

A jump table is a way to future proof your design.

Probably the best-known use of a jump table is in the Commodore “kernal,” which every eight-bit Commodore machine has had.

[barrym95838]

Several of the 6502 pioneers like Woz didn't bother with JMP tables or complex BRK handlers, although convoluted RTS tables were definitely on the menu. They packed their ROM code as tightly as they possibly could, and let the entry points fall where they may. Many of those entry points became "standard", like the Apple ]['s $FDED for COUT and -151 for the monitor prompt, and the burden fell on the person updating the ROM code in subsequent incarnations to keep that functionality as well as he or she could. When you're a pioneer (or just want to act like one), you can be afforded some artistic license in my book.