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: Mon, 16 Jan 2012 23:01:53 +0100 [thread overview]
Message-ID: <878vl7i9wu.fsf@pobox.com> (raw)
In-Reply-To: <87d3ajibga.fsf@pobox.com> (Andy Wingo's message of "Mon, 16 Jan 2012 22:28:37 +0100")
On Mon 16 Jan 2012 22:28, Andy Wingo <wingo@pobox.com> writes:
> On Mon 16 Jan 2012 20:46, Stefan Israelsson Tampe <stefan.itampe@gmail.com> writes:
>
>> why are these two not equal in the sense of bound-identifier=?
>>
> But that's not the right question or answer. Can you should where these
> identifiers come from?
Sorry, I've been making lots of typos recently. I meant to say, "can
you show where these identifiers come from?"
Andy
--
http://wingolog.org/
prev parent reply other threads:[~2012-01-16 22:01 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
2012-01-17 15:33 ` Stefan Israelsson Tampe
2012-01-16 22:01 ` Andy Wingo [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://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=878vl7i9wu.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).