I think I'll stick to a yearly cadence for calculator projects. This project started out on several Amtrak trips with inconsistent wifi, and I've gotten it up to a more functional state over the last few weeks. I waited until now to make this post out of a desire to avoid the "I made a post about this project that I will abandon in a few weeks" trap that I've fallen into before. At this point, I think I'll stick with the project until I hit a performance wall that halts my progress.
Currently, it finishes the startup sequence before infinite looping at the BASIC interpreter while it waits for a keyboard input that has not yet been coded. I recommend building with debug enabled so you can see the traces print out on CEmu because that is the most enjoyment you will get from the code right now. Did I mention that graphics are not included, either? If you enable tracing from the beginning of execution, make sure to unlock CEmu's emulation speed because I removed the opcode optimization to help aid with debugging.
Obligatory "I have not tested this on real hardware yet so test on real calculators at your own risk"
Link to GitHub repo
Currently, it finishes the startup sequence before infinite looping at the BASIC interpreter while it waits for a keyboard input that has not yet been coded. I recommend building with debug enabled so you can see the traces print out on CEmu because that is the most enjoyment you will get from the code right now. Did I mention that graphics are not included, either? If you enable tracing from the beginning of execution, make sure to unlock CEmu's emulation speed because I removed the opcode optimization to help aid with debugging.
Obligatory "I have not tested this on real hardware yet so test on real calculators at your own risk"
Link to GitHub repo