The problem is how to actually load (byte)code without the help of these functions. Thats why I've added Parrot_load_bytecode_direct. The "not direct" version can use parrotlib code to locate the specified file by iterating through a list of "directories" (or better Sub PMCs, as outlined by Dan).
We should add a Parrot_packfile_from_buffer(Interpreter, char *buf, long len) function to the API to load in bytecode files that are already in memory, and have the base parrot library be a big string constant in a simple C file somewhere. (Probably ought to be a .so too so it can be upgraded without having to rebuild parrot)
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
