Re: [Firebird-devel] Executing statement in the same context as external engine execution

2018-03-26 Thread Jiří Činčura
>If you prefer old ISC API and its additional overhead (note, ISC API > is a wrapper over It's more about a convenience (I have the bindings already in place from FB Embedded implementation) than preference. The OO API has one major drawback. It's OO. :) Passing objects between environments

[Firebird-devel] Getting location of fbclient.dll via IExternalContext

2018-03-26 Thread Jiří Činčura
Hi *, can I get location of currently used fbclient.dll via IExternalContext? Or the directory. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ -- Check out the vibrant tech community on one of the world's most en

Re: [Firebird-devel] Executing statement in the same context as external engine execution

2018-03-26 Thread Dimitry Sibiryakov
26.03.2018 17:12, Jiří Činčura wrote: The OO API has one major drawback. It's OO. It is not actually OO. It is just structures of plain function pointers. The only thing that is missed in this "OO API" is a structure with pointers to ISC functions. Such structure would solve the rest of pro

[Firebird-devel] Updating README.keywords

2018-03-26 Thread Mark Rotteveel
I just noticed that I should also have updated README.keywords in https://github.com/FirebirdSQL/firebird/pull/150 But as I need to update it anyway, is it OK if I do a slightly more thorough overhaul? I noticed that some of the words marked with * are actually marked as (non-)reserved word in

Re: [Firebird-devel] Getting location of fbclient.dll via IExternalContext

2018-03-26 Thread Jiří Činčura
Hmm, found `context->getMaster()->getConfigManager()->getRootDirectory()`. Is there a better/shorter way? And adding "fbclient.dll" is then trivial. So it works for me. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ -

Re: [Firebird-devel] Getting location of fbclient.dll via IExternalContext

2018-03-26 Thread Dimitry Sibiryakov
26.03.2018 17:49, Jiří Činčura wrote: Hmm, found `context->getMaster()->getConfigManager()->getRootDirectory()`. Is there a better/shorter way? Just use LoadLibrary() without path. The library is for sure already loaded into address space, so the function will return handle to it without f

Re: [Firebird-devel] Getting location of fbclient.dll via IExternalContext

2018-03-26 Thread Vlad Khorsun via Firebird-devel
26.03.2018 18:49, Jiří Činčura wrote: Hmm, found `context->getMaster()->getConfigManager()->getRootDirectory()`. Is there a better/shorter way? This is the best way, especially if there could be more than one fbclient.dll loaded by host process. And adding "fbclient.dll" is then trivial.

Re: [Firebird-devel] Getting location of fbclient.dll via IExternalContext

2018-03-26 Thread Jiří Činčura
>Just use LoadLibrary() without path. The library is for sure already > loaded into > address space, so the function will return handle to it without further > searching. I need the string. Not load the library. -- Mgr. Jiří Činčura https://www.tabsoverspaces.com/ ---

Re: [Firebird-devel] Updating README.keywords

2018-03-26 Thread Alex Peshkoff via Firebird-devel
On 03/26/18 18:37, Mark Rotteveel wrote: I just noticed that I should also have updated README.keywords in https://github.com/FirebirdSQL/firebird/pull/150 But as I need to update it anyway, is it OK if I do a slightly more thorough overhaul? I noticed that some of the words marked with * are

Re: [Firebird-devel] Getting location of fbclient.dll via IExternalContext

2018-03-26 Thread Jiří Činčura
> > Hmm, found `context->getMaster()->getConfigManager()->getRootDirectory()`. > > Is there a better/shorter way? > >This is the best way, especially if there could be more than one > fbclient.dll > loaded by host process. > > > And adding "fbclient.dll" is then trivial. So it works for me

Re: [Firebird-devel] Getting location of fbclient.dll via IExternalContext

2018-03-26 Thread Dimitry Sibiryakov
26.03.2018 18:04, Jiří Činčura wrote: Just use LoadLibrary() without path. The library is for sure already loaded into address space, so the function will return handle to it without further searching. I need the string. Not load the library. Then everything is even simplier: GetModuleHa