unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: Wolfgang J Moeller <wjm@heenes.com>
Cc: bug-guile@gnu.org
Subject: Re: scm_i_print_symbol_name() in libguile/print.c ...
Date: Mon, 11 Apr 2011 17:00:03 +0200	[thread overview]
Message-ID: <m3fwpon898.fsf@unquote.localdomain> (raw)
In-Reply-To: <alpine.LNX.2.00.1104111412380.13176@gwdw03.gwdg.de> (Wolfgang J. Moeller's message of "Mon, 11 Apr 2011 14:23:18 +0200 (CEST)")

Hi,

On Mon 11 Apr 2011 14:23, Wolfgang J Moeller <wjm@heenes.com> writes:

> Subsequently I noticed that `psyntax-pp.scm' is full of symbols
> #{name\ number}# which so far, would _not_ be read in
> as the original "gensym"s.
>
> This is going to change if you re-generate `psyntax-pp.scm'
> using the "fixed" GUILE. Hope it doesn't hurt ...

No, it doesn't.  The backslash was an accident, and anyway after fixing
the reader too #{foo\ bar}# reads the same as #{foo bar}#.  Those
symbols need to be unique lexically, but not globally, so it's not a big
deal.  At some point we will need globally unique gensyms but this
change does not adversely impact the current state of things.

Cheers,

Andy
-- 
http://wingolog.org/



  reply	other threads:[~2011-04-11 15:00 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-05 15:27 scm_i_print_symbol_name() in libguile/print.c Wolfgang J Moeller
2011-04-11 11:50 ` Andy Wingo
2011-04-11 12:23   ` Wolfgang J Moeller
2011-04-11 15:00     ` Andy Wingo [this message]
2011-04-11 11:50 ` Andy Wingo
2011-04-11 13:08   ` Wolfgang J Moeller
2011-04-11 15:16     ` 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=m3fwpon898.fsf@unquote.localdomain \
    --to=wingo@pobox.com \
    --cc=bug-guile@gnu.org \
    --cc=wjm@heenes.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).