Re: find-versioned-module bugs

[Julian Graham]

Hi Andy,


>  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?


>  2. Version order: Hoo, dunno. See above. Is "first compatible" the
>     right thing, or should we be smarter (and more wasteful)?

I don't feel strongly either way -- "smarter's" already working (I
think), but "first compatible" is pretty easy to move to.  Let me know
how you'd like to proceed and I'll make it so.

Sorry I've been sluggish about addressing these!


Regards,
Julian