From: Julian Graham <joolean@gmail.com>
To: Andy Wingo <wingo@pobox.com>
Cc: bug-guile <bug-guile@gnu.org>
Subject: Re: find-versioned-module bugs
Date: Thu, 10 Jun 2010 10:02:54 -0400 [thread overview]
Message-ID: <AANLkTiksPl7ErTlo8fgeq7b5hRMxfROLFwHoUD7AOFAL@mail.gmail.com> (raw)
In-Reply-To: <m3vd9rnkjy.fsf@pobox.com>
Hey Andy,
> Thanks! Now, a further request, which you may turn down of course :-).
> This function currently looks in all dirs in the load path for all ways
> that versions can be represented, hence the stat explosion. Instead of
> enumerating the entire set of compatible modules, why not simply stop
> with the first one? I suspect this would respect the user's expectations
> just as well.
>
> What do you think? :)
There's a method to the madness (if I understand the question) -- it
stems from an earlier conversation we (well, Neil and I) had [0] about
wanting to load the most recent version of a library when multiple
matches are available for a partially-specified version reference. So
just because we've found, say, a module with version (6 1) that
matches our version reference of (6), we might find a module with
version (6 2) further in our search. Of course, R6RS says:
"When more than one library is identified by a library reference, the
choice of libraries is determined in some implementation-dependent
manner."
So we can certainly change this behavior. Shall I go ahead and do that?
Regards,
Julian
[0] - http://www.mail-archive.com/guile-devel@gnu.org/msg03655.html
next prev parent reply other threads:[~2010-06-10 14:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-09 7:11 find-versioned-module bugs Andy Wingo
2010-06-09 12:40 ` Julian Graham
2010-06-10 4:25 ` Julian Graham
2010-06-10 12:23 ` Andy Wingo
2010-06-10 14:02 ` Julian Graham [this message]
2010-06-10 14:49 ` Andy Wingo
2010-06-14 22:53 ` Andy Wingo
2010-06-15 5:02 ` Julian Graham
2010-06-15 7:34 ` Andy Wingo
2010-06-17 12:58 ` Julian Graham
2010-06-18 8:28 ` Andy Wingo
2010-06-15 23:12 ` Ludovic Courtès
2010-06-16 7:23 ` Andy Wingo
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=AANLkTiksPl7ErTlo8fgeq7b5hRMxfROLFwHoUD7AOFAL@mail.gmail.com \
--to=joolean@gmail.com \
--cc=bug-guile@gnu.org \
--cc=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).