Completing a BASIC language interpreter in 2025
nanochess.org
Completing a BASIC language interpreter in 2025
1–10 of 22 posts
Re: Completing a BASIC language interpreter in 2025
#2Ah the Aquarius :) My uncle got one as a donation to his private little "museum" and all I remember was how different it looked from the other machines of that era and a game that taught you spelling by shooting down letters Space Invaders style.
Re: Completing a BASIC language interpreter in 2025
#3This is a very impressive project a really informative post, thanks to the author! There used to be a lot of content like this on the internet, I miss those days.
Re: Completing a BASIC language interpreter in 2025
#4Back in 2014, I stumbled on the original source code for the first version of Oregon Trail, which was written in a suspect of BASIC for a timeshare system used by the public schools in Minnesota (probably not the version you're thinking of https://en.wikipedia.org/wiki/The_Oregon_Trail_(1971_video_g...).
I was really into VR at the time and had been working on live-programmable VR environments, primarily through a text editor component that could render to a 3D object texture. As a demo of the component, I wrote a good-enough BASIC interpreter to ruin the Oregon Trail code.
Writing the interpreter was actually a lot of fun and not that hard, considering I already had a lot of code for processing code syntax for the syntax highlighting feature of the code editor.
Sadly, Web standards have changed a bit too much, I couldn't get traction on my project after Mozilla's AFrame released, so now it's some broken code sitting in a GitHub repo somewhere.
Re: Completing a BASIC language interpreter in 2025
#5Back in 2014, I stumbled on the original source code for the first version of Oregon Trail, which was written in a suspect of BASIC for a timeshare system used by the public schools in Minnesota (probably not the version you're thinking of https://en.wikipedia.org/wiki/The_Oregon_Trail_(1971_video_g... ). I was really into VR at the time and had been working on live-programmable VR environments, primarily through a t…
> a suspect of BASIC
subset?
Re: Completing a BASIC language interpreter in 2025
#6Ah the Aquarius :) My uncle got one as a donation to his private little "museum" and all I remember was how different it looked from the other machines of that era and a game that taught you spelling by shooting down letters Space Invaders style.
> a game that taught you spelling by shooting down letters Space Invaders style.
Sure it wasn't meant to teach typing? (Maybe I'm thinking of a different game...)
Re: Completing a BASIC language interpreter in 2025
#7Very impressive, as usual! I've never written a 100-page assembly program in my life, much less in one month. The string stack part reminded me of http://turboforth.net/downloads/docs/ANS_String_Lib.pdf, with the same motivation of handling string expressions in limited memory without needing a GC.
Re: Completing a BASIC language interpreter in 2025
#8Back in 2014, I stumbled on the original source code for the first version of Oregon Trail, which was written in a suspect of BASIC for a timeshare system used by the public schools in Minnesota (probably not the version you're thinking of https://en.wikipedia.org/wiki/The_Oregon_Trail_(1971_video_g... ). I was really into VR at the time and had been working on live-programmable VR environments, primarily through a t…
> a suspect of BASIC subset?
Dialect. Didn't notice the auto-incorrect.
Re: Completing a BASIC language interpreter in 2025
#9> a new BASIC interpreter for the 1983 Mattel ECS add-on for Intellivision
Fun fact: Hal Finney (yes, that Hal) wrote a BASIC interpreter for the Intellivision back in 1978 or so in a weekend. It was 2K of code. Mattel shipped it on a cartridge.
ROM space was so tight, the only error message it produced was:
EH?
Re: Completing a BASIC language interpreter in 2025
#10Very interesting, this is kind of cool.