From: Kevin Ryde <user42@zip.com.au>
Subject: Re: [PATCH] SRFI-34, SRFI-60 and core bindings
Date: Sat, 22 Oct 2005 06:36:50 +1000 [thread overview]
Message-ID: <87u0fabo9p.fsf@zip.com.au> (raw)
In-Reply-To: <87fyqvgvd1.fsf@laas.fr> (Ludovic Courtès's message of "Fri, 21 Oct 2005 09:52:26 +0200")
ludovic.courtes@laas.fr (Ludovic Courtès) writes:
>
> it does _not_ override the core
> binding, unlike `(use-modules (srfi srfi-60))' (with no renamer) in the
> current state. What it does is that is replaces this binding only
> within the module user: the binding replacement is confined.
Yes, I'm talking about the module user too, the module user loses some
core bindings.
> This is exactly the behavior users may expect.
If you don't know about the clashes/replacements then you're likely to
be unpleasantly surprised to see core stuff suddenly move under your
feet. But a way to acknowledge that in the use-modules might be nice.
An option for srfi-60 bit-count would be to extend the core, since the
argument types are different in the two forms. Such cases have been
using #:replace, eg. srfi-17 and srfi-39.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2005-10-21 20:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-20 13:09 [PATCH] SRFI-34, SRFI-60 and core bindings Ludovic Courtès
2005-10-20 19:42 ` Kevin Ryde
2005-10-21 7:52 ` Ludovic Courtès
2005-10-21 20:36 ` Kevin Ryde [this message]
2005-10-24 8:10 ` Ludovic Courtès
2005-12-06 23:23 ` Marius Vollmer
2005-12-07 10:10 ` Ludovic Courtès
2005-12-13 21:55 ` Marius Vollmer
2005-12-14 10:13 ` Ludovic Courtès
2005-12-28 20:14 ` Neil Jerram
2006-01-03 10:06 ` 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=87u0fabo9p.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).