Peter Dimov wrote:
entry_point will probably have to demangle the various "greet" exports and perform overload resolution and implicit conversions as necessary. This _is_ heavy machinery but it's hidden from the user and Boost.Python may already contain the bulk of the functionality.
If this is going to become the basis for a plugin system you probably want to have some versioning mechanism as well as some form of introspection, checksumming, etc. to catch the most common failures. In short, you will really end up developing a full-fledged component model. I'm not saying this is worthless. I'm just pointing out that a simple dlopen/dlsym mechanism won't be really useful without the rest, and it's this rest that will be hard to do, in particular if the goal is to provide a generic solution. Regards, Stefan