> 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? Which Hal was very proud of. He showed it to me to make me laugh. At the time I was programming the Mattel…
Completing a BASIC language interpreter in 2025
11–20 of 22 posts
Re: Completing a BASIC language interpreter in 2025
#12> 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? Which Hal was very proud of. He showed it to me to make me laugh. At the time I was programming the Mattel…
BootOS, the 512-byte OS written by Oscar Toledo (author of this article), also has a single error message, "Oops".
Re: Completing a BASIC language interpreter in 2025
#13Ah 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
#14It was a lot of fun. The assembler I used was really powerful; I used its macro facilities to create ‘rule’ macros that defined the BNF of the language.
Congrats on your own implementation!
Re: Completing a BASIC language interpreter in 2025
#15Very 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
#16> 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? Which Hal was very proud of. He showed it to me to make me laugh. At the time I was programming the Mattel…
That's hilarious. I wonder how many corners he cut on that. Is there a disassembly floating around somewhere?
I don't know that any listings were kept. It never occurred to me to save any of mine. Oh well.
Re: Completing a BASIC language interpreter in 2025
#17Earlier quoted context omitted.
That's hilarious. I wonder how many corners he cut on that. Is there a disassembly floating around somewhere?
It was written in assembly. I don't know that any listings were kept. It never occurred to me to save any of mine. Oh well.
One of the more interesting projects was to make an annotated listing of the 6809 version of MS Basic for the Dragon 32. We learned so much just by studying that code. It was only 16K and yet we spent months on that.
And for stuff we wrote ourselves, a real-time 3D renderer for simple 3D models in 6502 assembly was probably the pinnacle.
Re: Completing a BASIC language interpreter in 2025
#18Very 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.
First time I heard of it. I should know better as the TI-99/4A forum is just one click away from the Intellivision forum. Thanks for the heads up!
Re: Completing a BASIC language interpreter in 2025
#19Earlier quoted context omitted.
It was written in assembly. I don't know that any listings were kept. It never occurred to me to save any of mine. Oh well.
Likewise, I've lost all of my code from the 8 bit era, no big deal, really, but it would have been fun to read some of it. One of the more interesting projects was to make an annotated listing of the 6809 version of MS Basic for the Dragon 32. We learned so much just by studying that code. It was only 16K and yet we spent months on that. And for stuff we wrote ourselves, a real-time 3D renderer for simple 3D models i…
Re: Completing a BASIC language interpreter in 2025
#20Earlier quoted context omitted.
Likewise, I've lost all of my code from the 8 bit era, no big deal, really, but it would have been fun to read some of it. One of the more interesting projects was to make an annotated listing of the 6809 version of MS Basic for the Dragon 32. We learned so much just by studying that code. It was only 16K and yet we spent months on that. And for stuff we wrote ourselves, a real-time 3D renderer for simple 3D models i…
I was fortunate to have learned to code in an environment where a lot of excellent programmers were kind enough to help me out. For example, my roommate showed me how stacks worked. It was like magic!