From: Kevin Ryde <user42@zip.com.au>
Subject: Re: [PATCH] `any' and `every' in `(oop goops util)'
Date: Fri, 21 Oct 2005 05:47:14 +1000 [thread overview]
Message-ID: <87oe5k9dj1.fsf@zip.com.au> (raw)
In-Reply-To: <87psq0pmyy.fsf@laas.fr> (Ludovic Courtès's message of "Thu, 20 Oct 2005 11:16:37 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> Hi,
>
> The `(oop goops util)' module currently exports its own version of `any' and
> `every', which is unnecessary and causes warnings to be issued when
> `(srfi srfi-1)' is being used.
When using (oop goops) ? I'm not sure (oop goops util) is meant to be
used outside the goops implementation.
(There's a non-tail recursive mapappend which could probably benefit
from srfi-1 append-map too, incidentally.)
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-20 19:47 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 [this message]
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
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=87oe5k9dj1.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).