From: Andy Wingo <wingo@pobox.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-devel@gnu.org
Subject: Re: splicing macros
Date: Sun, 27 Jan 2013 11:17:22 +0100 [thread overview]
Message-ID: <87a9rv9bgt.fsf@pobox.com> (raw)
In-Reply-To: <5103d30a.6718700a.6306.350b@mx.google.com> (Stefan Israelsson Tampe's message of "Sat, 26 Jan 2013 14:03:20 +0100")
On Sat 26 Jan 2013 14:03, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
> I will assume that you are familliar with th ck macro, included in
> recent guile releases or else consider looking it up at
>
> http://okmij.org/ftp/Scheme/macros.html
It does not seem to be documented in Guile's manual. Want to write some
documentation? :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2013-01-27 10:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-26 13:03 splicing macros Stefan Israelsson Tampe
2013-01-27 10:17 ` Andy Wingo [this message]
2013-01-28 11:27 ` Stefan Israelsson Tampe
2013-02-08 20:53 ` Stefan Israelsson Tampe
2013-04-29 20:46 ` Fwd: " Stefan Israelsson Tampe
2014-03-20 20:32 ` Andy Wingo
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=87a9rv9bgt.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=stefan.itampe@gmail.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).