At present, a program which loads plugins (actually any run time shared library) can be linked to a thunk which preloads some plugins. In this case, run time load requests are satisfied by the preload if possible, otherwise a normal dynamic load is performed.
So at present, preloads *override* dynamic loads. I think it would be useful to add a second level of preloads which acts as a default if the dynamic load fails. So the priority order would be: 1. Overriding preloads 2. File system dynamic loads 3. Default preloads. Default preloads allow a binary to run, but the behaviour to be modified by "adding" a plugin which overrides the default. Comments? -- john skaller skal...@users.sourceforge.net http://felix-lang.org ------------------------------------------------------------------------------ CenturyLink Cloud: The Leader in Enterprise Cloud Services. Learn Why More Businesses Are Choosing CenturyLink Cloud For Critical Workloads, Development Environments & Everything In Between. Get a Quote or Start a Free Trial Today. http://pubads.g.doubleclick.net/gampad/clk?id=119420431&iu=/4140/ostg.clktrk _______________________________________________ Felix-language mailing list Felix-language@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/felix-language
