Hi there. Believe it or not, this issue was thrashed out years ago and the solution still in use today is called the Component Object Model - COM.
I've written a really simple implementation you can play with called v3c-dcom http://sourceforge.net/projects/v3c-dcom/ I had a look at some of the other proposals 1. enums identifying the platform this doesn't cover yet-to-be-developed platforms 2. functions returning void * if the right plug-in is present this doesn't cover cases where different platforms can support the same interface, like a pixmap fall-back for the display Continuing with your current approach you'll get to the stage where you realise that you don't simply want function pointers, you want interface pointers, with reference counting - I'm just trying to save you some time. I'd be happy to change the names of the functions in v3c-dcom should any similarity to Microsoft's naming scheme cause a fuss. This could be Qt's new plug-in system. Regards, Philip Ashmore _______________________________________________ Qt5-feedback mailing list [email protected] http://lists.qt.nokia.com/mailman/listinfo/qt5-feedback
