unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: "Andy Wingo" <wingo@pobox.com>
Cc: guile-devel@gnu.org
Subject: Re: GNU Guile branch, master, updated. v2.1.0-102-g0f9f51a
Date: Wed, 09 Nov 2011 23:36:45 -0500	[thread overview]
Message-ID: <87boskzj8i.fsf@netris.org> (raw)
In-Reply-To: <E1RNMul-0000TQ-6L@vcs.savannah.gnu.org> (Andy Wingo's message of "Mon, 07 Nov 2011 10:58:55 +0000")

Hi Andy,

> commit de41e56492666801078e73860a358e1c63cbc8c2
> Author: Andy Wingo <wingo-e+AXbWqSrlAAvxtiuMwx3w@public.gmane.org>
> Date:   Fri Nov 4 19:34:22 2011 +0100
> 
>     hygienically rename macro-introduced bindings, reproducibly
>     
>     * module/ice-9/psyntax.scm (chi-top-sequence): Detect bindings to
>       identifiers introduced by macros.  In that case, in order to preserve
>       hygiene, uniquify the variable's name, but in a way that is
>       reproduceable (i.e., yields the same uniquified name after a
>       recompile).

What method do you use to uniquify a macro-introduced top-level name,
such that a recompile yields the same name?  I have doubts that this is
possible without breaking hygiene in some cases.

     Mark



       reply	other threads:[~2011-11-10  4:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1RNMul-0000TQ-6L@vcs.savannah.gnu.org>
2011-11-10  4:36 ` Mark H Weaver [this message]
2011-11-10  8:34   ` GNU Guile branch, master, updated. v2.1.0-102-g0f9f51a Andy Wingo
2011-11-10 16:46     ` Mark H Weaver
2011-11-11 20:20       ` Ludovic Courtès
2011-11-15 20:58         ` Andy Wingo
2011-11-15 21:12       ` Andy Wingo
2011-11-16  3:58         ` Mark H Weaver
2012-01-06 17:47           ` Andy Wingo
2012-01-14 20:37             ` Mark H Weaver
2012-01-14 20:54               ` David Kastrup
2012-01-14 21:39                 ` Mark H Weaver
2012-01-14 22:01               ` dsmich
2012-01-14 23:40               ` Ludovic Courtès
2012-01-15 11:44               ` 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=87boskzj8i.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=guile-devel@gnu.org \
    --cc=wingo@pobox.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).