Question

I’m designing (brainstorming) a C++ plugin framework for an extensible architecture.
Each plugin registers an interface, which is implemented by the plugin itself.
Such framework may be running on relatively capable embedded devices (e.g. Atom/ARM) so I can use STL and Boost.

At the moment I’ve managed to write a similar framework, in which interfaces are known in advance and plugins (loaded from dynamic libraries) register the objects implementing them. Those objects are instantiated as needed by their factory methods, and methods are called correctly.

Now I want to make it more flexible, having plugins register new interfaces (not just implementing the existing ones) thus extending the API available to the framework users.

I thought of using a std::map<std::string, FunctionPtr>, which is also mentioned by several articles and stackoverflow replies I’ve read. Unfortunately it doesn’t seem to capture the case of different method interfaces.

I feel it might have something to do with template metaprogramming, or traits perhaps, but I can’t figure out how it should work exactly. Can anyone help?

Answer 1

Try looking at XPCOM which solves these problems for you – by sortof re-implementing COM.

You have the issue of not knowing what interface the plugin provides to your application, so you need a way for the developer to access it, without the compiler knowing what it is (though, if you supply a header file, then suddenly you do know what it is and you can compile it without any need for plugin unknown-interface fanciness)

so, you’re going to have to rely on runtime determinism of the interface, that roughly requires you to define the interface in some way so that the framework can call arbitrary methods on it, and I think the only realistic way you can do that is to define each interface as a set of function pointers that are loaded individually and then stored in data for the user to call. And that pretty much means a map of function pointers to names. It also means you can only user compiler niceties (such as overloading) by making the function names unique. The compiler does this for you by ‘mangling’ all functions to unique, coded names.

Type Traits will help you wrap your imported functions in your framework, so you can inspect them and create classes that work with any imported type, but it isn’t going to solve the main problem of importing arbitrary functions.

Possibly one approach that you’ll want to read is Metaclasses and Reflection by Vollmann. This was referenced by the C++ standard body, though I don’t know if it will become part of a future spec. Alternatively you can look at Boost.Extension