3 ms·
It's actually quite amazing that it's possible to run Lisp in 48k of RAM, but it is. http://www.flownet.com/ron/plisp.html http://www.flownet.com/ron/plisp.htm
by lisper 8y ago
It's actually quite amazing that it's possible to run Lisp in 48k of RAM, but it is.
http://www.flownet.com/ron/plisp.html http://www.flownet.com/ron/plisp.html
- forinti 8y agoI used a Pascal on a BBC Micro which consisted of 2 16KB ROMS: one for the editor and one for the compiler. It would have maybe 32KB of RAM minus the screen memory (1KB to 20KB).
- rbanffy 8y ago32K for an editor?! That's insane! If I'm not clear, that's insanely huge for an 8-bit computer.
- forinti 8y agoI think the editor was just one of the 16KB ROMS. But you are right. Wordwise was an incredible text editor and it also fitted in a 16KB ROM. 32KB was the total RAM you had on a BBC Micro B.
- Heliodromus 8y agoActually... I was co-author of Acorn ISO Pascal. The system fit in two 16KB EPROMS for a total of 32KB, but only one of the 16KB ROMS could be mapped into the address space at a time. The way this worked was that the compiler was self-hosted (i.e. written in ISO Pascal and compiled itself) and generated our own stack-based virtual machine code which we referred to as BL-code based on our own initials. One of the 16K ROMS contained the BL-code of the self-compiled compiler... which only fit after a considerable amount of effort, including a few "macro" BL-codes designed for the purpose. Remember this was full BSI-certified ISO-Pascal, plus Acorn extensions for graphics etc, not some toy subset. The other 16K ROM contained everything else, meaning the BL-code interpreter, screen editor, run-time libraries (floating point - which we copied from BBC basic, Pascal I/O, heap, etc), and command line interpreter. The editor, which I wrote, was around 4KB and fairly sophisticated for the time, including full regex global replace. One interesting tidbit is how the system actually ran given that the compiler was in one ROM, and the interpreter needed to run it in the other ROM, with only one ROM able to be mapped into the address space at a time... The way we handled this was to relocate the interpreter into RAM in order to run the compiler (but run from ROM when running user programs), so the interpreter was organized into pure code, pure data and relocatable address tables to make this possible. Getting the whole system to fit into those two 16K ROMS was a heck of a challenge!
- rbanffy 8y agoHaving grown up in Brazil, I never had contact with the BBC micros until I became interested in retro computing. What you folks accomplished is not appreciated enough on the other side of the Atlantic.
- jgrahamc 8y agoWhy do you find it incredible? It really depends on many features you want to implement. I had LISP in ROM on my BBC Micro. That was about 5.5K of code (6502) on the ROM plus some data. The machine had 32KB of RAM.
- Someone 8y agohttp://history.siam.org/sup/Fox_1960_LISP.pdf http://history.siam.org/sup/Fox_1960_LISP.pdf: ”The current basic LISP system uses about 12,000 of the 32,000 memory of the IBM 704.” The 704 was 36 bits, so that 12,000 was 54 kilobytes. Speed-wise, the 704 had more and larger registers, but ran slower than a 6502 (about 40 kHz for a 704 according to http://bitsavers.org/pdf/ibm/704/24-6661-2_704_Manual_1955.pdf http://bitsavers.org/pdf/ibm/704/24-6661-2_704_Manual_1955.p... vs about a MHz for typical 6502s) On the plus side, the 704 did multiplications and divisions. https://www-03.ibm.com/ibm/history/exhibits/mainframe/mainframe_PP704.html https://www-03.ibm.com/ibm/history/exhibits/mainframe/mainfr... gives it about 4,000 multiplications or divisions per second. I think that’s quite a bit faster than a 6502, on 36 bit words, but you don’t need 36-bit arithmetic for a LISP. It also had floating point, but you don’t need that for a LISP, either.