2 ms·
Design a byte code like Sweet 16 or UCSD Pascal, and compile Ruby to that. It would certainly be more space/time efficient than Manx Aztec C, which was terribl
by DonHopkins 3y ago
Design a byte code like Sweet 16 or UCSD Pascal, and compile Ruby to that.
It would certainly be more space/time efficient than Manx Aztec C, which was terrible.
https://en.wikipedia.org/wiki/Aztec_C https://en.wikipedia.org/wiki/Aztec_C
Hilarious discussion on the talk page -- I used Aztec C but I have not vanished yet:
https://en.wikipedia.org/wiki/Talk:Aztec_C#WHO_vanished%3F https://en.wikipedia.org/wiki/Talk:Aztec_C#WHO_vanished%3F
I had a Legend Industries 128KDE memory expansion card on my Apple ][+ -- that would help!
Washington Apple PI, January 1982, p. 12, "I CAN'T REMEMBER HOW MUCH MEMORY I HAVE" by David Morganstein:
https://www.wap.org/journal/showcase/washingtonapplepijournal1982v4no1jan82.pdf https://www.wap.org/journal/showcase/washingtonapplepijourna...
- colanderman 3y ago.NET/MSIL is actually somewhat reasonable. I'm working on a loader+interpreter for the //e right now.