From: Andy Wingo <wingo@pobox.com>
To: Julian Graham <joolean@gmail.com>
Cc: bug-guile <bug-guile@gnu.org>
Subject: Re: find-versioned-module bugs
Date: Tue, 15 Jun 2010 00:53:29 +0200 [thread overview]
Message-ID: <m3eig9jkeu.fsf@pobox.com> (raw)
In-Reply-To: <m3bpbjndsl.fsf@pobox.com> (Andy Wingo's message of "Thu, 10 Jun 2010 16:49:14 +0200")
On Thu 10 Jun 2010 16:49, Andy Wingo <wingo@pobox.com> writes:
> In our case, my opinion is that we should change the rule to be, "the
> first compatible version found in the path"; though perhaps we should
> wait for confirmation from Ludovic.
I was just looking at the current situation, and there are a few bugs.
1. Precompiled files are never used; only the fallback path (~/.cache)
is used. This is because resolve-module calls `load' in the
versioned case, and only `primitive-load-path' scours
`%load-compiled-path'. The solution is going to be complicated, and
require some refactoring. I don't want to implement the mtime dance
again.
2. Version order: Hoo, dunno. See above. Is "first compatible" the
right thing, or should we be smarter (and more wasteful)?
Any thoughts? :)
Andy
--
http://wingolog.org/
next prev parent reply other threads:[~2010-06-14 22:53 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
2010-06-10 14:49 ` Andy Wingo
2010-06-14 22:53 ` Andy Wingo [this message]
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=m3eig9jkeu.fsf@pobox.com \
--to=wingo@pobox.com \
--cc=bug-guile@gnu.org \
--cc=joolean@gmail.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).