Re: find-versioned-module bugs

[Andy Wingo]

Hi Julian,

On Thu 10 Jun 2010 16:02, Julian Graham <address@hidden> writes:

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

Well, not to contradict Neil, but I do think changing is the right
answer. In http://www.mail-archive.com/address@hidden/msg03655.html
you had asked:

> > * Should we establish some rules for what you get when you don't
> > specify a version?

And Neil replied:

> Yes!  The latest available?

While this was a noble sentiment, and a consistent strategy, it's not
the right thing IMO. Versions were not a well-considered addition to the
spec, and we should not feel compelled to (a) promote them, or (b) to
implement them ideally (according to their ideals).

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.

Cheers,

Andy
-- 
http://wingolog.org/