12.11.2015 21:33, Dimitry Sibiryakov wrote: > 12.11.2015 20:12, Vlad Khorsun wrote: >> How much ? Do yo know way better ? > > Not much, I agree. But still it is excess. > >> Do yo know way better ? > > Yep. As I said, good old style plugins: separate library for each, a > definite entry > point for each type which returns ready-to-use plugin class instead of > pointless factory.
I see no good reason to force people to isolate tightly coupled plugins from each other just because you not understand difference between module initialization and creation of plugin instance. >> Look at >> >> PluginSet PluginManager::getPlugins(Status status, uint pluginType, >> const string namesList, >> FirebirdConf firebirdConf) >> >> Look at second parameter. Nobody prevents you to load plugins of any kind. > > Second parameter is not a big deal here. Third one is tricky. Put it into configuration of that plugin which is aware of your "special" plugin. For example, you create "engine_by_aafemt" and "replication_by_aafemt" plugin's. You put "engine_by_aafemt" into Providers setting of firebird.conf and "replication_by_aafemt" into Replication setting of engine_by_aafemt.conf. >> Config PluginManager::getConfig(Status status, const string filename); >> >> should suit your needs > > Sure. Unless I want my plugin to be listed in firebird.conf among other > plugins. But > that's my own cockroaches, you don't need to care. And i don't care, don't worry ;) Regards, Vlad ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
