From: Kevin Ryde <user42@zip.com.au>
Subject: Re: srfi-1 delete proc arg order
Date: Fri, 16 May 2003 11:06:53 +1000 [thread overview]
Message-ID: <87ptmjem36.fsf@zip.com.au> (raw)
In-Reply-To: <87of26eo6p.fsf@zagadka.ping.de> (Marius Vollmer's message of "13 May 2003 19:44:46 +0200")
Marius Vollmer <mvo@zagadka.de> writes:
>
> The SRFI must win, so we have to break backwards compatability.
At least it wasn't specified in the guile docs, so hopefully noone
will depend on it.
> Kevin, please make the change in 1.6 as well and put a nice big note
> at the top of NEWS.
Done.
(I take it the branch NEWS gets copied to the head at a suitable time,
so I only added there.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-05-16 1:06 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
2003-05-16 1:06 ` Kevin Ryde [this message]
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=87ptmjem36.fsf@zip.com.au \
--to=user42@zip.com.au \
/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).