From: Andy Wingo <wingo@pobox.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] Undeprecate read syntax for uniform complex vectors
Date: Wed, 06 Apr 2011 20:54:43 +0200 [thread overview]
Message-ID: <m362qrrz0s.fsf@unquote.localdomain> (raw)
In-Reply-To: <87sjtwxnmv.fsf@netris.org> (Mark H. Weaver's message of "Tue, 05 Apr 2011 19:51:52 -0400")
On Wed 06 Apr 2011 01:51, Mark H Weaver <mhw@netris.org> writes:
> FYI, I just pushed this fix.
>
> * libguile/read.c (scm_read_sharp): Move the "#c..." case outside of
> #if SCM_ENABLE_DEPRECATED, and to the same section which handles
> "#s...", "#u..." and "#f...".
> Thanks to Andreas Rottmann <a.rottmann@gmx.at> for the bug report.
Thanks! What bug does it fix? Sorry for being obtuse :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2011-04-06 18:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-05 23:51 [PATCH] Undeprecate read syntax for uniform complex vectors Mark H Weaver
2011-04-06 18:54 ` Andy Wingo [this message]
2011-04-06 20:20 ` Mark H Weaver
2011-04-06 21:10 ` Andy Wingo
2011-04-06 20:37 ` Andreas Rottmann
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=m362qrrz0s.fsf@unquote.localdomain \
--to=wingo@pobox.com \
--cc=guile-devel@gnu.org \
--cc=mhw@netris.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).