From: Andy Wingo <wingo@pobox.com>
To: Mike Gran <spk121@yahoo.com>
Cc: bug-guile@gnu.org
Subject: Re: [r6rs] #\x0 is a perfectly valid character datum representation
Date: Sat, 17 Jul 2010 13:38:30 +0200 [thread overview]
Message-ID: <m34ofy49u1.fsf@unquote.localdomain> (raw)
In-Reply-To: <841747.50551.qm@web37906.mail.mud.yahoo.com> (Mike Gran's message of "Sat, 17 Jul 2010 04:22:35 -0700 (PDT)")
Hi,
On Sat 17 Jul 2010 13:22, Mike Gran <spk121@yahoo.com> writes:
>> >> r6rs hex *character* escapes and Guile 1.8.x octal
>
>> >> character escapes could logically coexist without confusion.
>>
>> > Let's do that. Shall you, or shall I?
>
> I pushed this change into git.
Thanks a lot!
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-07-17 11:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-17 11:22 [r6rs] #\x0 is a perfectly valid character datum representation Mike Gran
2010-07-17 11:38 ` Andy Wingo [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-06-21 8:12 Marco Maggi
2010-06-21 19:26 ` Andy Wingo
2010-06-21 20:27 ` Mike Gran
2010-06-21 20:36 ` Andy Wingo
2010-06-21 20:42 ` Mike Gran
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=m34ofy49u1.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=spk121@yahoo.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).