Reader Macros in Common Lisp(lisper.in)
lisper.in
Reader Macros in Common Lisp
http://lisper.in/reader-macros/
6 comments
(Speaking as an Open Dylan hacker...)
I've occasionally wondered if we should take the old emulator sources and re-package them as a separate repository. It isn't clear that anyone knows how to make them run any longer or whether or not they'd run on anything other than LispWorks or if this would be of anything other than a historical curiosity.
I've occasionally wondered if we should take the old emulator sources and re-package them as a separate repository. It isn't clear that anyone knows how to make them run any longer or whether or not they'd run on anything other than LispWorks or if this would be of anything other than a historical curiosity.
It's things like this that remind me that Lisp(s) are really the best languages for taking advantage of the idea of Turing completeness. In terms of ease of implementation that is. I think that really, this is what we mean by "powerful" languages - how easily can you take advantage of the principle of completeness to do anything in your chosen language.
You often hear people using the idea of completeness to say that their favourite language can, of course, do anything. But in reality some languages just aren't very well suited to it, or would require some horrendous amount of coding and abstractions (Greenspuns Tenth rule comes to mind [1]).
So whenever some new idea in programming becomes popular, whether it's pattern matching [2], concurrency [3], or even the web (HN), you can always rest easy because someone will be able to quite quickly write that functionality into Lisp itself. The only difficulty is in finding out about the libraries in the first place!
[1] https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule [2] https://github.com/m2ym/optima [3] http://lparallel.org/
You often hear people using the idea of completeness to say that their favourite language can, of course, do anything. But in reality some languages just aren't very well suited to it, or would require some horrendous amount of coding and abstractions (Greenspuns Tenth rule comes to mind [1]).
So whenever some new idea in programming becomes popular, whether it's pattern matching [2], concurrency [3], or even the web (HN), you can always rest easy because someone will be able to quite quickly write that functionality into Lisp itself. The only difficulty is in finding out about the libraries in the first place!
[1] https://en.wikipedia.org/wiki/Greenspun%27s_tenth_rule [2] https://github.com/m2ym/optima [3] http://lparallel.org/
I often read that Ruby (or Forth, for that matter) is great for DSL because you can "misuse" the language tokenizer/parser directly as parser for your DSL, as long as it's similar enough to ruby (e.g. tokens are whitespace delimited and such). Unfortunately, Ruby's macro power is nowhere near LISP.
I wasn't aware that this is possible in LISP, too. That's really great!
I wasn't aware that this is possible in LISP, too. That's really great!
Certain things are still hardwired into the Common Lisp reader. For example, because of how colons are treated in symbols, you can't trivially support something like JSON via reader macros. It still works best if the input bears a pretty good resemblance to lisp.
That's not such a big deal, because there are plenty of tools for conventional input parsing in Common Lisp.
That's not such a big deal, because there are plenty of tools for conventional input parsing in Common Lisp.
There are a few languages that are good for (internal) DSL, ie. Dialects - https://news.ycombinator.com/item?id=8394181
Unfortunately the Dialecting wikipedia link given in above comment now just redirects to http://en.wikipedia.org/wiki/Dialect_(computing)
The original page listed... Forth, Lisp, Rebol, Ruby & XL - https://web.archive.org/web/20140708161345/http://en.wikiped...
Unfortunately the Dialecting wikipedia link given in above comment now just redirects to http://en.wikipedia.org/wiki/Dialect_(computing)
The original page listed... Forth, Lisp, Rebol, Ruby & XL - https://web.archive.org/web/20140708161345/http://en.wikiped...
Great article! I've used reader macros to implement readers for little assembly languages. It's also super-awesome that Lisp has this nice compiler right under the floor boards. And I don't have to touch any parser generators.
Love this. Since readmacros aren't an everyday topic but rather out of the way and related to special purposes, there aren't that many practical introductions. This article is a nice writeup.
The author has taken a great care to communicate his ideas clearly in such a way that is a pleasure to read it. Very well done!
When Dylan went from prefix to infix syntax the reader macro indirection got all the more elaborate: what started out as a trivial reader macro that treated colons differently started delegating to a full-blown lex & yacc style parser instead.
All the better, most of this was achieved modularly: Lisp editor buffers and Lisp listeners would run happily alongside Dylan editor buffers and Dylan listeners, Lisp code could still compile load and run alongside Dylan code, and Lisp classes could interoperate cleanly with Dylan classes.
There's no question that Common Lisp and its predecessors are some of the most formidably adaptable and hackable programming environments ever created. Only Smalltalk really comes close, and they have complementary strengths I think. Standard macros, reader macros and a comprehensive MOP are some of the key things that stand out in Common Lisp's favour in that hackability comparison.