From: ludovic.courtes@laas.fr (Ludovic Courtès)
Cc: guile-devel@gnu.org
Subject: Re: [PATCH] `any' and `every' in `(oop goops util)'
Date: Thu, 08 Dec 2005 08:51:24 +0100 [thread overview]
Message-ID: <871x0oauwz.fsf@laas.fr> (raw)
In-Reply-To: <87mzjcelu0.fsf@ossau.uklinux.net> (Neil Jerram's message of "Wed, 07 Dec 2005 19:41:43 +0000")
Neil Jerram <neil@ossau.uklinux.net> writes:
> Couldn't we then remove any and every from util.scm, and change
> goops.scm to use (srfi srfi-1)? This will catch anyone who has used
> (oop goops util) to get any/every, but that's an odd thing to do and
> we can cover it in a NEWS item.
Agreed. I might give it a try next week if nobody did it by then.
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
prev parent reply other threads:[~2005-12-08 7:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 9:16 [PATCH] `any' and `every' in `(oop goops util)' Ludovic Courtès
2005-10-20 19:47 ` Kevin Ryde
2005-10-21 7:54 ` Ludovic Courtès
2005-10-21 20:38 ` Kevin Ryde
2005-10-24 7:45 ` Ludovic Courtès
2005-12-06 23:11 ` Marius Vollmer
2005-12-07 9:59 ` Ludovic Courtès
2005-12-07 19:41 ` Neil Jerram
2005-12-08 7:51 ` Ludovic Courtès [this message]
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=871x0oauwz.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
--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).