From: Ken A. <kan...@bb...> - 2003-06-21 22:49:15
|
At 05:57 PM 6/21/2003 -0400, Timothy John Hickey wrote: >Hi Jscheme afficionados, > > I've started using the ability to load from a URL and its very nice. One problem is >occurs when we load a file F from a URL and that file contains non-URL load statements. >The natural interpretation would be to look for these embedded loads on that remote URL >(just as happens with relative links in webpages), but currently Jscheme looks for those >files locally. It should be pretty easy to get around this problem (keep a stack of URLs >and always use the top of the stack for loads). > >What do you think? Am I missing some unintended consequence? maybe you've found two (or more) features of JScheme that need to be combined in a better way, certainly in a way that hasn't been tried before. The normal (load f) tries to open an input port treating f as first a file, then a resource, and then a URL.. This order was chosen because the .scm file would be in a local file before it gets moved into a jar file for a delivered application. I've never thought about the URL case. JScheme has a dynamic class path, and perhaps such a URL should be added to that path. What are you trying to do? |