From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: [PATCH] scm_module_variable, duplicate bindings handlers
Date: Fri, 10 Aug 2007 16:53:31 +0200 [thread overview]
Message-ID: <873ayrh250.fsf@chbouib.org> (raw)
In-Reply-To: 87sl6rn2b4.fsf@pobox.com
Hi Andy,
Andy Wingo <wingo@pobox.com> writes:
> 1) misordered-module-variable-lookup.patch, fixes the lookup order in
> scm_module_variable to be like 1.8, which allows binders to run at the
> correct time
See comments below.
> 2) duplicate-binding-use-module-variable.patch, fixes the duplicate
> bindings handlers to lookup the resolved values using module-variable
> rather than module-local-variable, as it is possible that public
> interfaces use other modules.
Ok, sounds good.
> --- modules.c.~1.65.~ 2007-05-05 22:38:57.000000000 +0200
> +++ modules.c 2007-08-10 11:33:50.000000000 +0200
> @@ -418,15 +418,8 @@
> if (SCM_BOUND_THING_P (b))
> return b;
>
> - /* 2. Search imported bindings. In order to be consistent with
> - `module-variable', the binder gets called only when no imported binding
> - matches SYM. */
> - b = module_imported_variable (module, sym);
> - if (SCM_BOUND_THING_P (b))
> - return SCM_BOOL_F;
> -
> {
> - /* 3. Query the custom binder. */
> + /* 2. Query the custom binder. */
The rationale here was to be consistent with `module-variable', but it
admittedly sounds questionable to look for imported variables here.
> - /* 2. Search among the imported variables. */
> - var = module_imported_variable (module, sym);
> - if (SCM_BOUND_THING_P (var))
> - return var;
> -
> {
> - /* 3. Query the custom binder. */
> + /* 2. Query the custom binder. */
Here, the rationale was that invoking the custom binder is expensive and
should be done as a last resort.
OTOH, given how `module-autoload!' is implemented, it probably doesn't
make any difference performance-wise to do things in the order you
suggest, and it seems more consistent since it allows local variables to
always override imported variables.
So both patches make sense.
You'll need to assign copyright to the FSF for Guile, though. We can
discuss it privately if you want.
Thanks!
Ludovic.
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
next prev parent reply other threads:[~2007-08-10 14:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-10 9:53 [PATCH] scm_module_variable, duplicate bindings handlers Andy Wingo
2007-08-10 14:53 ` Ludovic Courtès [this message]
2007-08-13 9:08 ` Neil Jerram
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=873ayrh250.fsf@chbouib.org \
--to=ludo@gnu.org \
--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).