Werner LEMBERG w...@gnu.org writes:
I find the above much too dense. It introduces three different pseudo
operators in one rush. While tightly related, it should be done step
by step. So this is a criticism of the R6RS docs (being a standard to
be read by Scheme experts), not LilyPond.
If I break down the example I listed before, here are a few
useful ways of applying it:
This is much easier to understand, thanks. However:
; this $@ produces elements for a sequential music list via map!. Each
; element is constructed from p, a list of pitches making up a chord,
; and
Werner LEMBERG w...@gnu.org writes:
If I break down the example I listed before, here are a few
useful ways of applying it:
This is much easier to understand, thanks. However:
; this $@ produces elements for a sequential music list via map!. Each
; element is constructed from p, a list
(map! + '(1 2 3) '(4 5 6)) = (5 7 9)
You must not! not! not! use map! on constant lists.
Interesting. This is something non-obvious, at least after reading
the Guile documentation. Now, knowing what you've just written, a
second read makes much more sense, and I can see that this
Trevor Daniels t.dani...@treda.co.uk writes:
Comment #16 on issue 2607 by d...@gnu.org: Patch: Allow immediate Scheme
expressions to take multiple values
http://code.google.com/p/lilypond/issues/detail?id=2607
Good idea documenting this, though. That way people have a chance to
The inspiration for this ,@ is described as
If an `(unquote-splicing expression ...)' form appears inside a
qq template, then the expressions must evaluate to lists; the
opening and closing parentheses of the lists are then stripped
away and the elements of the lists
