From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: richard@rshann.plus.com
Cc: "guile-user@gnu.org" <guile-user@gnu.org>
Subject: Re: Syntactic significance of dot
Date: Mon, 22 Sep 2014 20:43:57 +0200 [thread overview]
Message-ID: <CAMFYt2aoPSyogAHoL8BMpSi642bc=RWED8BEe0czh3yQw=zvnQ@mail.gmail.com> (raw)
In-Reply-To: <CAMFYt2aD6FqnXx6wAhCFoXwTRW+_JDd1-1dHQTkPwNuOhJH3pw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 208 bytes --]
A little more errata :)
[sorry for the confusion]
> This behaviour is coherent in the context of quasiquote:
> (let ((a 1) (b 2) (c 3))
> `(,a ,b . ,c))
> yields
> (1 2 3)
>
Should be:
yields
(1 2 . 3)
[-- Attachment #2: Type: text/html, Size: 646 bytes --]
next prev parent reply other threads:[~2014-09-22 18:43 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 [this message]
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='CAMFYt2aoPSyogAHoL8BMpSi642bc=RWED8BEe0czh3yQw=zvnQ@mail.gmail.com' \
--to=godek.maciek@gmail.com \
--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).