From: Andy Wingo <wingo@pobox.com>
Subject: Re: bug: list-index overloaded
Date: Mon, 27 Nov 2006 12:18:41 +0100 [thread overview]
Message-ID: <1164626321.3756.20.camel@localhost.localdomain> (raw)
In-Reply-To: <ekc8ae$us0$1@sea.gmane.org>
Hi Han-Wen,
On Sun, 2006-11-26 at 15:28 +0100, Han-Wen Nienhuys wrote:
> ice-9/boot.scm defines a list-index (list, elt), which is in conflict
> with srfi's list-index (pred list) function.
>
> please fix.
This has been the case for a long time, and would be an incompatible
change, breaking code in not-very-comprehensible ways. Sometimes I avoid
importing srfi-1 for this reason. Perhaps for Rob's 2.0 vision?
Andy
--
http://wingolog.org/
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2006-11-27 11:18 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-26 14:28 bug: list-index overloaded Han-Wen Nienhuys
2006-11-26 16:25 ` Neil Jerram
2006-11-26 16:43 ` Han-Wen Nienhuys
2006-11-27 11:18 ` Andy Wingo [this message]
2006-11-27 21:51 ` Neil Jerram
2006-11-28 20:12 ` 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=1164626321.3756.20.camel@localhost.localdomain \
--to=wingo@pobox.com \
/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).