From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: What is wrong with these few lines of guile code?
Date: Sat, 4 Nov 2017 12:46:04 +0100 [thread overview]
Message-ID: <20171104114604.GA16111@thebird.nl> (raw)
In-Reply-To: <0086dc34-2b3a-25f6-2420-2dfe18568e13@crazy-compilers.com>
On Fri, Nov 03, 2017 at 03:34:23PM +0100, Hartmut Goebel wrote:
> Am 31.10.2017 um 18:50 schrieb Christopher Baines:
> > This matches the error you're getting, as #~ is short for (gexp ...) as
> > I understand it.
>
> Thanks you, this did the trick :-) Although this reminds my on the magic
> signs in perl :-(
It is not magic (unlike Perl). In Guile you can use almost any
character to give something a name. This does not come natural to us
non-Lisp programmers. The #~ is merely an agreed convention to name
certain macros. And macros, essentially, are syntax expansions. No
magic. Though macros can do magic, but that is a different story ;)
Pj.
prev parent reply other threads:[~2017-11-04 11:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-31 13:41 What is wrong with these few lines of guile code? Hartmut Goebel
2017-10-31 14:02 ` Mike
2017-10-31 17:50 ` Christopher Baines
2017-11-03 14:34 ` Hartmut Goebel
2017-11-03 16:09 ` Ricardo Wurmus
2017-11-04 11:46 ` Pjotr Prins [this message]
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20171104114604.GA16111@thebird.nl \
--to=pjotr.public12@thebird.nl \
--cc=guix-devel@gnu.org \
--cc=h.goebel@crazy-compilers.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).