From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: bug-guile@gnu.org
Subject: Re: peval error
Date: Fri, 16 Sep 2011 17:43:34 -0700 [thread overview]
Message-ID: <87d3f09ex5.fsf@pobox.com> (raw)
In-Reply-To: <87zki4pzyi.fsf@gnu.org> ("Ludovic Courtès"'s message of "Fri, 16 Sep 2011 12:02:29 +0200")
Hi,
On Fri 16 Sep 2011 03:02, ludo@gnu.org (Ludovic Courtès) writes:
> Renaming one of the #{x2 2899}# fixes the problem.
Yes, whenever you introduce a new binding (for example, by inlining),
you will need to rename the newly bound variable.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-09-17 0:43 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-10 17:35 peval error Andy Wingo
2011-09-10 23:05 ` Ludovic Courtès
2011-09-13 17:04 ` Ludovic Courtès
2011-09-15 18:23 ` Andy Wingo
2011-09-15 21:44 ` Ludovic Courtès
2011-09-16 10:02 ` Ludovic Courtès
2011-09-17 0:43 ` Andy Wingo [this message]
2011-09-17 10:31 ` Ludovic Courtès
2011-09-17 14:52 ` Ludovic Courtès
2011-09-17 17:54 ` Andy Wingo
2011-09-18 10:00 ` bug#9542: " Ludovic Courtès
2011-09-18 21:05 ` Ludovic Courtès
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=87d3f09ex5.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=ludo@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).