From: Dmitry Dzhus <mail@sphinx.net.ru>
To: guile-user@gnu.org
Subject: Re: Looping local binding
Date: Sat, 03 Nov 2007 13:46:48 +0300 [thread overview]
Message-ID: <871wb7fvxj.fsf@sphinx.net.ru> (raw)
In-Reply-To: JQQI18$BE1739F41A01350DD56F36909E9338C1@poste.it
That's terrific, Marco, and that code is almost clear to me.
I'm now strongly convinced that I should introduce myself to Scheme
macro forms closer. What may a recommended definite guide to it? (I
read SICP, but that book concentrates on other kind of things).
--
Happy Hacking.
Dmitry Dzhus
http://sphinx.net.ru
_______________________________________________
Guile-user mailing list
Guile-user@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-user
next prev parent reply other threads:[~2007-11-03 10:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-30 17:03 Looping local binding Marco Maggi
2007-11-03 10:46 ` Dmitry Dzhus [this message]
2007-11-03 11:12 ` Neil Jerram
2007-11-03 18:33 ` Keith Wright
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 16:28 Dmitry Dzhus
2007-10-29 22:12 ` Neil Jerram
2007-11-03 10:46 ` Dmitry Dzhus
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=871wb7fvxj.fsf@sphinx.net.ru \
--to=mail@sphinx.net.ru \
--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).