LispCraft

Hi, all. I finally completed Warcraft 2 implementation in LISP.
http://img859.imageshack.us/i/52320836.png/

Took me a few months, though, but mostly because I was too lazy and my DSL is still pretty buggy, has poor debugging support and long compilation times (takes about 30 seconds to reload source file). Anyway, this proves, that writing a game in Lisp is relatively easy, even for a single person.

>>89
No. How would you parse <A < B = C>: <(A < B) = C> or <A (<B = C>)?

>>90
<A in <A (<B = C>) has no left-hand side.
Even D < A < B = C > would work because after D it should expect an operator, not another operand.
There are also various precedence rules you could apply.

>>91
*wouldn't

>>91
<A in <A (<B = C>) has no left-hand side.
Usually <...> is part of some larger expression, like [X <A < B = C> Y]

Even D < A < B = C > would work because after D it should expect an operator, not another operand.
How about (list D < A < B = C >)? Why not (list (D < A) (< B = C >))?

>>91
What about (list < A < B = C >)? It will be parsed as ((list < A) ..)