From: ludovic.courtes@laas.fr (Ludovic Courtès)
Subject: Re: [PATCH] `any' and `every' in `(oop goops util)'
Date: Mon, 24 Oct 2005 09:45:13 +0200 [thread overview]
Message-ID: <87irvnmk8m.fsf@laas.fr> (raw)
In-Reply-To: <87pspybo6a.fsf@zip.com.au> (Kevin Ryde's message of "Sat, 22 Oct 2005 06:38:53 +1000")
Hi,
Kevin Ryde <user42@zip.com.au> writes:
> If you're not supposed to use it then any warnings it provokes when
> you do aren't a big deal :).
Right. ;-)
> Now that srfi-1 has a lot more C code it's probably worth using for
> performance.
Yes, that's the point I was trying to make: this module had better use
SRFI-1 as much as possible (also for maintainability and consistency
reasons).
Thanks,
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-24 7:45 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 [this message]
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=87irvnmk8m.fsf@laas.fr \
--to=ludovic.courtes@laas.fr \
/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).