We could just go with the dull "list of directories" approach, but that's already shown to be sub-optimal--people want to wedge in archives, code blocks, sockets, and other bizarre things. So what do we want to do?
At the moment I'm thinking of the load path as an array of subs that get passed in the file being looked for and return... something. I'm not sure what, though.
I'm also not sure if load_bytecode and other ops should search the path at all, or if they should take absolute locations, with all the searching done by provided (but guaranteed) library code. (I think I like this one as well)
Discussion time, I think.
--
Dan--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
