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 13:50:46 +0200 [thread overview]
Message-ID: <m3oc4dm2g9.fsf@unquote.localdomain> (raw)
In-Reply-To: <alpine.LNX.2.00.1104051619430.26447@gwdw03.gwdg.de> (Wolfgang J. Moeller's message of "Tue, 5 Apr 2011 17:27:46 +0200 (CEST)")
Hi Wolfgang,
On Tue 05 Apr 2011 17:27, Wolfgang J Moeller <wjm@heenes.com> writes:
> scm_i_print_symbol_name() in libguile/print.c ought not insert backslashes
> into "weird" symbol names that it prints using #{ ... }#,
> because the "extended read syntax" (in agreement with the documentation)
> doesn't treat backslashes specially, nor _usually_ needs escaping. (*)
>
> I notice that the bug is already present in GUILE V1.8 .
Indeed, good catch. I had seen this before but didn't fully understand
it.
> (*) 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.
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-04-11 11:50 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 [this message]
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=m3oc4dm2g9.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).