What about the following (also considering, that we might not like one handle/mmap... per PMC, as stated in one f'up):
A dynamic PMC library has one init function returning a dyn_pmc_info structure:
I think I'd rather have pre-defined names in the PMC library that we can call like any other function in a dynamically loaded library. We just pick a pair of names that can be mashed appropriately and are done with it.
The big issue is one of metadata. The point about having multiple classes in a single library is well-taken, but there's the issue of how we keep track of which things are in which files. While there's still the issue of finding those files in a library tree, if there's a 1-to-1 relation between classes and files it gets a bit simpler.
We probably want some sort of metadata system on disk, though I'm loathe to go that way.
--
Dan
--------------------------------------"it's like this"-------------------
Dan Sugalski even samurai
[EMAIL PROTECTED] have teddy bears and even
teddy bears get drunk
