Re: find-versioned-module bugs

[Andy Wingo]

Hi Julian,

On Tue 15 Jun 2010 07:02, Julian Graham <address@hidden> writes:

>>  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.
>
> Ah, yes, I remember -- FWIW, `find-versioned-module' was supposed to
> be a version-aware formulation of `primitive-load-path'.  Well, uh,
> what should we do?  I don't suppose it'd make sense to move some of
> the precompiled-file-checking code from `primitive-load-path' into a
> place where it could be used by, say, `primitive-load', would it?

I don't know, all that code is tricky. How about having
find-versioned-module return a tail instead of a full path, then pass
that tail to primitive-load-path? It will cause some slight duplication
of effort but it will find the .go correctly.

Andy
-- 
http://wingolog.org/