Re:Kilo LISP
by aaronharder on Tuesday March 19, 2019 @08:09AM
(#19430032)
I 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.
Re:Kilo LISP
by nils-m-holm on Tuesday March 19, 2019 @08:48AM
(#19430227)
Aaronharder 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!
Thanks. 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?
Re:Kilo LISP
by nils-m-holm on Tuesday March 19, 2019 @11:21AM
(#19431623)
Sounds like a solid argument, but I think I will stick to the "kilo byte order of magnitude" narrative! :)
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?