David Brown wrote:
I think there is a lot to learn from the reader of common lisp, since it
shows how a parser can be written in an extensible way. A lot is just that
it isn't a very difficult language to parse.
And I will assert that you are *wrong*.
Lisp (as s-expressions) is particularly *annoying* to parse. Parsing
the following expression is a PITA:
('() 1 2 '(2 . 3) . 4) or perhaps if you want to watch your stack blow:
'((((((((('())))))))))
Sure, these are contrived pathological cases, but they tend to be *real*
cases after a macroexpander gets done with code.
People generally implement the language they are writing for in that
language. If anything, it helps you make sure that you've done things
right.
Uh, not even *close* to generally. C is done in C. Java is done in
Java. And? Perl ... C. Python ... C, Java, C#. Tcl ... C. Ruby ...
C, Java, C#. Lua ... C. Javascript ... C.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-lpsg
