From: Richard Shann <richard@rshann.plus.com>
To: guile-user@gnu.org
Subject: Syntactic significance of dot
Date: Mon, 22 Sep 2014 19:12:36 +0100 [thread overview]
Message-ID: <1411409556.3458.145.camel@DebianBox.loc> (raw)
I've come across some (working) scheme code whose meaning I can't
unravel. The problem is there is a "." character whose significance
eludes me. The guile reference doesn't index this character, and I can
only find references to it in writing literal pairs.
But I'm sure someone experienced would recognize what this could be (the
dot occurs on the eleventh line):
(define (ignatzek-format-exception
root
exception-markup
bass-pitch
lowercase-root?)
(make-line-markup
`(
,(name-root root lowercase-root?)
,exception-markup
.
,(if (ly:pitch? bass-pitch)
(list (ly:context-property context 'slashChordSeparator)
(name-note bass-pitch #f))
'()))))
Richard Shann
next reply other threads:[~2014-09-22 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 18:12 Richard Shann [this message]
2014-09-22 18:32 ` Syntactic significance of dot Panicz Maciej Godek
2014-09-22 18:38 ` Panicz Maciej Godek
2014-09-22 18:43 ` Panicz Maciej Godek
2014-09-22 21:01 ` Marko Rauhamaa
2014-09-23 8:49 ` Richard Shann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1411409556.3458.145.camel@DebianBox.loc \
--to=richard@rshann.plus.com \
--cc=guile-user@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).