3 ms·
Is Scheme as good as Common Lisp?
I think Scheme doesn't have the all-powerful Macros, so would one be missing out on all the LISP goodness for choosing Scheme?
How usable are Macros, anyway? Does their use tend to produce readable code?
- davidw 19y agoYes, but both are widely considered inferior to Visual Forth ++.
- brlewis 19y agoR5RS hygienic macros qualify as LISP goodness, but a lot of Scheme implementations also implement defmacro (like CL) and/or syntax-case. Use of macros makes the code reflect the programmer's thinking about the problem domain. Whether this is readable or not depends on the programmer.
- pg 19y agoScheme has a way of defining macros that's supposed to be better than old-fashioned defmacro. These "hygienic macros" seemed to a lot of people (though not me) to be a good idea when they were invented. They got into the Scheme standard then. I think people don't like them so much now, but once something gets into a standard it's impossible to get it out. However (a) all the Scheme implementations I know of have implemented classic defmacro macros as well, and (b) if one hadn't, you could easily write it yourself. So in practice there's not much of a decision to make. The Arc implementation you're using to read this is written on top of Scheme. Currently Mzscheme.
- Tichy 19y agoThanks for the info! I learned Scheme with a rather obscure implementation (LMU Scheme, from my university), so I wasn't aware of the Macro capabilities of Scheme. Edit: I just checked, LMU Scheme is based on R4RS and indeed has no Macros.
- omouse 19y agoHygienic macros do seem to be a good idea: "Hygienic macros are macros whose expansion is guaranteed not to cause collisions with existing symbol definitions." (from Wikipedia, http://en.wikipedia.org/wiki/Hygienic_macro http://en.wikipedia.org/wiki/Hygienic_macro) What are the disadvantages? Is there any reason to dislike defining syntax rules?
- abstractbill 19y agoOne reason I've heard is that sometimes you actually want those collisions (I haven't come across a good example though - anyone know of one?). For me the reason is just that defmacro is easier to read.
- pg 19y agohere's one: (defmacro aif (test then &optional else) `(let ((it ,test)) (if it ,then ,else)))
- abstractbill 19y agoAh, of course - thanks!
- edw 19y agoIn Scheme, the cases where one would use anaphoric IF can be handled using a COND clause with a "=>": (cond ((assoc 'key collection) => (lambda (it) (do-something-with it))) (else (alternative))) Alternatively, if you really wanted to create an AIF macro, you could use SYNTAX-RULES to create something that sugared up the above thusly: (aif it (assoc 'key collection) (do-something-with it) (alternative)) Or you could, going outside the standard, use SYNTAX-CASE (ugh, in R6RS) or one of the other non R5RS approaches to macros e.g. syntactic closures[1] that don't throw out the macro hygiene baby with the occasional slight inconvenience bath-water. I'm a bit of a reformed macrologist; if I get an idea for a cool macro, I try to see how far I can take a non-macrotic version and compare that to what the syntactically-sugared version would be like. Most of the time, I wind up not bothering with a macro. I put macros in the same category as EVAL: If you think you need to use a macro, think again. [1]: (http://community.schemewiki.org/?syntactic-closures http://community.schemewiki.org/?syntactic-closures)
- euccastro 19y agoI'm not much into macros yet, but while syntax-case is a R6RS feature, I thought there is a portable implementation that runs on top of R5RS? At least Chicken 2.6 provides that, and its implementor is viscerally against R6RS.
- omouse 19y agoMacros produce kickass code: http://neverfriday.com/blog/?p=10#more-10 http://neverfriday.com/blog/?p=10#more-10 If I didn't create a string-case= macro, I would have to write the final expression over and over again. With multiple string-case matches I would have to write string=? many many times: (cond ((or (string=? "hello" my-string) (string=? "world" my-string)) (print "match"))) To do that with the string-case= macro: (string-case= my-string (("hello" "world") (print "match"))) Saves quite a bit of typing and now I have a good example of why macros are good to have around :D edit: formatting ftw.
- centipede 19y agoThat should possible with a higher-order-function (and a lambda), too.
- euccastro 19y agoThat only saves you one quote and one lambda for each clause, right? (define (string-case= my-string . clauses) (cond ((null? clauses) 'whatever) ((string-member? my-string (caar clauses)) ((cadar clauses))) (else (apply string-case= my-string (cdr clauses))))) Where string-member? is trivial to define as a procedure too. Then you use it like (string-case= ('("hello" "world") (lambda () (print "match")))) I myself wouldn't use a macro for this little gain. [Edit: I had completely misunderstood the macro.]
- brlewis 19y agoIf you put spaces in front of your code, news.yc will indent nicely. (cond ((or (string=? "hello" my-string) (string=? "world" my-string)) (print "match"))) (string-case= my-string (("hello" "world") (print "match")))