From: Matthias Koeppe <mkoeppe@mail.math.uni-magdeburg.de>
Subject: Re: srfi-1 delete and delete!
Date: Tue, 08 Jul 2003 10:20:04 +0200 [thread overview]
Message-ID: <uw565mdv39n.fsf@lambda.math.uni-magdeburg.de> (raw)
In-Reply-To: <87r851lvv2.fsf@zip.com.au> (Kevin Ryde's message of "Tue, 08 Jul 2003 10:12:33 +1000")
Kevin Ryde <user42@zip.com.au> writes:
> I wrote:
>>
>> This is new srfi-1 delete and delete!, as threatened.
>
> I made this change, and the new delete-duplicates too.
Maybe you also want to merge my new implementation of srfi-1
partition. I sent it to guile-devel on June 19, Message-ID
<uw5vfv2vz3h.fsf@saturn.math.uni-magdeburg.de>.
--
Matthias Koeppe -- http://www.math.uni-magdeburg.de/~mkoeppe
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2003-07-08 8:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-06-22 0:17 srfi-1 delete and delete! Kevin Ryde
2003-07-08 0:12 ` Kevin Ryde
2003-07-08 8:20 ` Matthias Koeppe [this message]
2003-07-09 22:59 ` Kevin Ryde
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=uw565mdv39n.fsf@lambda.math.uni-magdeburg.de \
--to=mkoeppe@mail.math.uni-magdeburg.de \
/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).