3 ms·
"Kilo LISP A Kilo Byte-Sized LISP System" But it's 25k of code, the executables and memory requirements are both greater than 1k. Did it start off as 1k in si
by benj111 8y ago
"Kilo LISP
A Kilo Byte-Sized LISP System"
But it's 25k of code, the executables and memory requirements are both greater than 1k.
Did it start off as 1k in size, and since expanded?
- S4M 8y agoI think they named it like that because it's 1k lines of code.
- aaronharder 8y agoI suspect it's called Kilo Lisp because all those sizes are in the of "kilobyte" order of magnitude, rather than "megabyte." But not because any aspect of it is exactly 1k in size. Fun name either way.
- nils-m-holm 8y agoAaronharder is right, it is called Kilo LISP, because it's code size is measured in kilo bytes. In fact the code contracted a bit since the first version. That being said, I like S4M's explanation, too!
- benj111 8y agoThanks. Wasn't sure if it started as a 1k thing. Sloccount on kl.c gives 1056, so either lose 56 lines, or 32 lines and put up with pedants. Edit: Making specialp() return a single line, excluding 1 branch of the #ifdef and all the #defines gets you below 1024. So maybe you could argue the case?
- nils-m-holm 8y agoSounds like a solid argument, but I think I will stick to the "kilo byte order of magnitude" narrative! :)