From: Wolfgang J Moeller <wjm@heenes.com>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile@gnu.org, Wolfgang J Moeller <wjm@heenes.com>
Subject: Re: scm_i_print_symbol_name() in libguile/print.c ...
Date: Mon, 11 Apr 2011 15:08:51 +0200 (CEST) [thread overview]
Message-ID: <alpine.LNX.2.00.1104111456180.13176@gwdw03.gwdg.de> (raw)
In-Reply-To: <m3oc4dm2g9.fsf@unquote.localdomain>
On Mon, 11 Apr 2011, Andy Wingo wrote:
>[...]
> > (*) Apparently, reading a "weird" symbol whose name contains "}#"
> > isn't provided for.
>
> Also; irritating. Relatedly it does not seem that Guile supports R6RS
> hex escapes in symbols. I guess the right thing to do is to allow for
> R6RS hex escapes in symbols, and escape '}', along with anything that's
> not a printable character.
Having any sort of escapes mixed with #{ }# notation would be incompatible -
maybe you ought no longer generate #{ }# on output, but switch to R6RS escapes
throughout. Since there has been (in my understanding) no way to read symbols
containing "}#" so far, just keep the "transparent" treatment of those
guile-private brackets on input.
Best regards,
Wolfgang J. Moeller, Tel. +49 551 47361, wjm<AT>heenes.com
37085 Goettingen, Germany | Disclaimer: No claim intended!
http://www.wjmoeller.de/ -+-------- http://www.heenes.com/
next prev parent reply other threads:[~2011-04-11 13:08 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
2011-04-11 11:50 ` Andy Wingo
2011-04-11 13:08 ` Wolfgang J Moeller [this message]
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=alpine.LNX.2.00.1104111456180.13176@gwdw03.gwdg.de \
--to=wjm@heenes.com \
--cc=bug-guile@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).