I think this is a mistake, but at the moment I'm not clever enough to
figure out how to properly acknowledge an end-of-list without a special
sentinel, which I'm trying to avoid.
TODO: Revisit this.
Modified Makefile to produce JUnit-compatible error messages.
Style (coffee-lint cleanup)
Updated metacadr's test suite to ensure that re-using a
metacadr-generated function does not lead to crashes. Saw this a lot in
early versions of LISP.
Lists are mutable, even by-reference. When I was popping off the values,
I was destroying the list; metacadr only worked once. That was terrible
functional programming. I should learn to trust myself; by using a
cons-list for my operations index and a lookup table (anti-if!)
for my operations, the code was simplified incredibly.
Also, added a very (!) primitive pretty printer. It'll get better over
time, but for now it's sufficient for debugging.
Elf M. Sternberg