On 12/11/2015 17:18, Vlad Khorsun wrote: > 12.11.2015 20:24, Adriano dos Santos Fernandes wrote: > ... >> BTW, another info the plugin entry point could receive now: the library >> filename. >> >> This way it can load additional configuration files, for example. >> >> That can be obtained by it himself, but it's trick, it's platform dependent. > Are you kidding ? Can I ask you too be less stupid?
Do you know that things like dladdr (and maybe binreloc) had problems in some architectures? Firebird 3 is the version I more dislike, it's full of not discussed things, and gratuitous stupidity in this list was one of the reasons. That include the plugin system. It was born in the original external engines, before even the Firebird 3 trunk was open. It had all the things I need, but suddenly, a new undiscussed plugin system appeared removing everything and broken my already done work. >> The engine already knows the filename it's loading, it could pass it. it >> could libe in IPluginInitialization. > "Could be" is not "must be" :) > > There is ConfigManager interface accessible from > Master::getConfigManager(), it allows > to know every "special" directory, including /plugins dir. > > Your think is so limited. Why would one would not just synlink the main plugin file in Firebird plugins directory and want to load the others files based on the real library filename path? Adriano ------------------------------------------------------------------------------ Firebird-Devel mailing list, web interface at https://lists.sourceforge.net/lists/listinfo/firebird-devel
