>>80
I think they keep forgetting that Lisp is written in Lisp on top of a bunch of primitives: all the CLOS systems, the Prometheus prototype OO system, Racket's class system, all the other OO systems,
loop,
iterate,
foof-loop, Shivers'
loop, Racket's
for,
match, optional and keyword arguments to
lambda, condition/exception systems, lazy evaluation (
delay,
lazy,
force), ...
I can continue, but I think it's enough. I'd like to know how he'd write a pattern matcher that doesn't feel like an hack (i.e. usable in real world without feeling dirty) in Ruby.