From: Andy Wingo <wingo@pobox.com>
To: Stefan Israelsson Tampe <stefan.itampe@gmail.com>
Cc: guile-devel <guile-devel@gnu.org>
Subject: Re: bound identifiers
Date: Tue, 17 Jan 2012 00:30:04 +0100 [thread overview]
Message-ID: <87y5t7gr9f.fsf@pobox.com> (raw)
In-Reply-To: <CAGua6m3mRn9YDi3v4MvybPwESTAUzNGBGA50b6C-17L-i+t3Jw@mail.gmail.com> (Stefan Israelsson Tampe's message of "Mon, 16 Jan 2012 22:56:44 +0100")
On Mon 16 Jan 2012 22:56, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
> As you see, it's just wild west to get the racket code working.
:)
Can you give a stripped-down test case for this particular behavior?
That code is paged into my and Mark's minds right now :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2012-01-16 23:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 19:46 bound identifiers Stefan Israelsson Tampe
2012-01-16 21:28 ` Andy Wingo
2012-01-16 21:56 ` Stefan Israelsson Tampe
2012-01-16 23:30 ` Andy Wingo [this message]
2012-01-17 15:33 ` Stefan Israelsson Tampe
2012-01-16 22:01 ` 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=87y5t7gr9f.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).