unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@pobox.com>
To: ludo@gnu.org (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [Guile-commits] GNU Guile branch, syncase-in-boot-9, updated. e3c5df539640a36eb1493f581087d54a4714f337
Date: Sun, 31 May 2009 14:14:01 +0200	[thread overview]
Message-ID: <m363fhpj06.fsf@pobox.com> (raw)
In-Reply-To: <8763fip2sf.fsf@gnu.org> ("Ludovic Courtès"'s message of "Sun, 31 May 2009 01:52:00 +0200")

Howdy,

Thanks for the review!

On Sun 31 May 2009 01:52, ludo@gnu.org (Ludovic Courtès) writes:

>> commit 34f3d47df9311852ba7eab6f8d1c36535c3774dd
>> Author: Andy Wingo <wingo@pobox.com>
>> Date:   Thu May 28 14:49:33 2009 +0200
>
> [...]
>
>>     * module/ice-9/boot-9.scm: Remove #' read-hash extension, which actually
>>       didn't do anything at all. It's been there since 1997, but no Guile
>>       code I've ever seen uses it, and it conflicts with #'x => (syntax x)
>>       from modern Scheme.
>
> I find this point questionable.  Do we really need to break this
> functionality?  It would be nicer if we could both keep
> `read-hash-extend' and the functionality you want.  What do you think?

`read-hash-extend' is still there. This just removed the #'
read-hash-extension, which was the identity extension: #'foo == foo.

`read-hash-extend' overrides any core hash forms, so this extension
prevented #'foo == (syntax foo). It would be easy for an affected reader
to add this particular extension back, though.

> (Besides, this commit appears to contain unrelated changes.

They are all described by the commit log, right? It is true that some of
the changes are not related to others, though. I'll try to separate them
out more in the future.

> Also, I
> prefer it when the test case appears in the same commit as the feature
> it tests, for easier review.)

OK.

> You may also want to add "SRFI-62 support" in `NEWS'.

Yes, and to the cond-expand forms. I have a lot of things I need to add
to NEWS before the release.

Cheers,

Andy
-- 
http://wingolog.org/




  reply	other threads:[~2009-05-31 12:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <E1M9fJa-0005yO-5y@cvs.savannah.gnu.org>
2009-05-30 23:52 ` [Guile-commits] GNU Guile branch, syncase-in-boot-9, updated. e3c5df539640a36eb1493f581087d54a4714f337 Ludovic Courtès
2009-05-31 12:14   ` Andy Wingo [this message]
2009-06-02 22:35     ` Neil Jerram
2009-06-04 19:16       ` Andy Wingo
2009-06-04 20:51         ` Neil Jerram

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=m363fhpj06.fsf@pobox.com \
    --to=wingo@pobox.com \
    --cc=guile-devel@gnu.org \
    --cc=ludo@gnu.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).