From: Marius Vollmer <mvo@zagadka.de>
Cc: guile-devel@gnu.org
Subject: Re: srfi-1 delete proc arg order
Date: 13 May 2003 19:44:46 +0200 [thread overview]
Message-ID: <87of26eo6p.fsf@zagadka.ping.de> (raw)
In-Reply-To: <877k8vrai4.fsf@raven.i.defaultvalue.org>
Rob Browning <rlb@defaultvalue.org> writes:
> Kevin Ryde <user42@zip.com.au> writes:
>
> > I applied this change to the head, someone else can make an
> > executive decision about the 1.6 branch.
>
> Marius, any opinion? Technically it's a bug fix as measured against
> the documentation, but if people have already accomodated this bug in
> their code, and just not said anything, the change would mean breakage
> for them...
Tough call. We just _can't_ offer a SRFI-1 that doesn't work like the
SRFI document says. That would be silly. It's also impossible to fix
this in a backwards compatible way.
The SRFI must win, so we have to break backwards compatability.
Kevin, please make the change in 1.6 as well and put a nice big note
at the top of NEWS.
--
GPG: D5D4E405 - 2F9B BCCC 8527 692A 04E3 331E FAF8 226A D5D4 E405
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-13 17:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-10 3:59 srfi-1 delete proc arg order Kevin Ryde
2003-05-12 23:03 ` Kevin Ryde
2003-05-12 23:49 ` Rob Browning
2003-05-13 17:44 ` Marius Vollmer [this message]
2003-05-16 1:06 ` Kevin Ryde
2003-05-16 2:26 ` Rob Browning
2003-05-16 23:37 ` Kevin Ryde
2003-05-17 0:06 ` Rob Browning
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=87of26eo6p.fsf@zagadka.ping.de \
--to=mvo@zagadka.de \
--cc=guile-devel@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).