On Wed, 2009-05-13 at 18:24 -0500, Eduardo Cavazos wrote: > Many Scheme implementations offer a way to specify a list of locations > to search for libraries. I think the rule for resolving a library to its > source should be configurable on a per location basis.
That's a good idea and worth developing, but it introduces more complexity, so I think a simpler single rule for files only should be standardized first, and then it could be integrated into something which does what you're suggesting. > I prefer resolvers that work like this: > > (a b c) => "a/b/c/c.sls" How about (a b c) => "a/b/c/^main^.sls". See my next post. > And the R6RS authors think you might want to access the source from a > database! Because the abstraction should be like that. Libraries just exist somewhere and your code should only care that they're somehow-who-cares available for importing. This way code is more portable into the long-term future when our operating systems are (hopefully very different) than now. > You could do stuff like this: > > (http-resolver "http://crop-circles.info/libraries";) > > and the implementation would treat the remote list of files as a source > of libraries, downloading them as necessary. I also hope that in the future libraries can be transparently retrieved from remote locations. The devil is in the details... -- : Derick ----------------------------------------------------------------
