From: Rob Browning <rlb@defaultvalue.org>
Subject: Re: libguile/print.c fixes
Date: Mon, 05 May 2003 20:28:17 -0500 [thread overview]
Message-ID: <87ade0zwwe.fsf@raven.i.defaultvalue.org> (raw)
In-Reply-To: <m3of2hm643.fsf@multivac.cwru.edu> (Paul Jarc's message of "Mon, 05 May 2003 17:32:38 -0400")
prj@po.cwru.edu (Paul Jarc) writes:
> Symbol names containing \ don't strictly need to be printed in
> #{this}# style, but it would significantly simplify the code if they
> were. Any objections?
Not sure. It's nice to avoid the escaping when you don't need it, but
I'm not sure how much complexity that introduces.
If we have to scan the symbol at construction time anyway, I wonder if
there's any clever way we could just set a flag (bit) that says
whether or not the symbol name needs escape encoding when we create
it? Do we have any unused symbol bits lying around?
--
Rob Browning
rlb @defaultvalue.org, @linuxdevel.com, and @debian.org
Previously @cs.utexas.edu
GPG starting 2002-11-03 = 14DD 432F AE39 534D B592 F9A0 25C8 D377 8C7E 73A4
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-06 1:28 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-05 21:32 libguile/print.c fixes Paul Jarc
2003-05-06 1:25 ` Rob Browning
2003-05-17 19:55 ` Marius Vollmer
2003-05-06 1:28 ` Rob Browning [this message]
2003-05-06 14:51 ` Paul Jarc
2003-05-17 20:01 ` Marius Vollmer
2003-05-19 14:52 ` Paul Jarc
2003-05-19 15:04 ` Marius Vollmer
2003-06-27 15:58 ` Paul Jarc
2003-06-30 22:40 ` Paul Jarc
2003-07-22 15:27 ` patch ping (was: libguile/print.c fixes) Paul Jarc
2003-07-22 16:42 ` Marius Vollmer
2003-07-22 16:47 ` patch ping Paul Jarc
2003-07-27 16:35 ` Marius Vollmer
2003-07-28 16:38 ` Paul Jarc
2003-09-15 12:39 ` Marius Vollmer
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=87ade0zwwe.fsf@raven.i.defaultvalue.org \
--to=rlb@defaultvalue.org \
/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).