From: Marko Rauhamaa <marko@pacujo.net>
To: richard@rshann.plus.com
Cc: guile-user@gnu.org
Subject: Re: Syntactic significance of dot
Date: Tue, 23 Sep 2014 00:01:13 +0300 [thread overview]
Message-ID: <87sijj1iau.fsf@elektro.pacujo.net> (raw)
In-Reply-To: <1411409556.3458.145.camel@DebianBox.loc> (Richard Shann's message of "Mon, 22 Sep 2014 19:12:36 +0100")
Richard Shann <richard@rshann.plus.com>:
> 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.
That's what it's for and nothing else, including in your example.
(a b . c)
is equivalent to
(a . (b . c))
Marko
next prev parent reply other threads:[~2014-09-22 21:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-22 18:12 Syntactic significance of dot Richard Shann
2014-09-22 18:32 ` 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 [this message]
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=87sijj1iau.fsf@elektro.pacujo.net \
--to=marko@pacujo.net \
--cc=guile-user@gnu.org \
--cc=richard@rshann.plus.com \
/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).