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/[email protected]/msg03655.html
