|
George_George wrote: Generally speaking using GetProcAddress through ordinal is faster than through name, right?
If you mean that strcmp is slower than indexing an array I agree. But I don't think this kind of optimization really matters in applications.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
Thanks CPallini,
I ask this question only for pure technical interest. Do you mean in your experience or in theory by ordinal is faster? Why?
regards,
George
|
|
|
|
|
George_George wrote: Do you mean in your experience or in theory by ordinal is faster? Why?
I've no big experience of DLL calls via GetProcAddress since I usually use load time linking approach.
Anyway I never experience performance issues.
My previous post points out that lookup using integers is usually faster that the one using strings, but, IMHO the performance improvement is usually negligible.
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
Thanks CPallini,
1.
You mean you use implicit linking to link with import library?
CPallini wrote: use load time linking approach
2.
If we use the approach as you used above, to link with import library, in this approach, there is no ways to use by ordinal technique?
regards,
George
|
|
|
|
|
George_George wrote: If we use the approach as you used above, to link with import library, in this approach, there is no ways to use by ordinal technique?
No, as the functions will be called via the linked stubs in the library.
I have never tried to explicitly load a DLL which has already been loaded by its lib.
Let's think the unthinkable, let's do the undoable, let's prepare to grapple with the ineffable itself, and see if we may not eff it after all.
Douglas Adams, "Dirk Gently's Holistic Detective Agency"
|
|
|
|
|
Thanks jhwurmbach,
From your reply, I understand by ordinal only works when we use LoadLobrary, if we use implicit linking, there is no way to use by ordinal.
regards,
George
|
|
|
|
|
in implicit linking, linker generates export library, then it will do in the optimised possible way right? why do you think implicit linking is not using ordinal, it gives a stub which internally uses ordinal values to link. That is why normally if you rebuild DLL, u need to rebuild the application too, if it looks up using name rebuilding is not needed.
George_George wrote: if we use implicit linking, there is no way to use by ordinal.
DEF files if you need to set ordinals explicitly
see this quote
"Implicit linking looks up based on the ordinal, so ideally a function's ordinal should always stay the same. Unless you specify your own ordinals the linker may generate different ordinals each time you build your application. This in turn means that Applications which have already been built to use your DLL may cease to link correctly."
from
DLL linking[^]
u may get more info if u searched on web.
|
|
|
|
|
Thanks Rajkumar,
I think it means when using implicit linking, ordinal of DLL exported function is built into EXE. EXE is using the ordinal value to look into related address array of exported function of the DLL to invoke related function, right?
Rajkumar R wrote: Implicit linking looks up based on the ordinal,
regards,
George
|
|
|
|
|
George_George wrote: ordinal of DLL exported function is built into EXE.
in a way yes, as the export library stub is linked to exe.
export library is generated through linker switch, it uses DEF files and /or dllexport keywords.
DEF files can be used to override the automatically generated ordinals, and as names can be used in DEF files, i think in that case export library uses names to link. But by default dllexport and export library uses ordinals.
|
|
|
|
|
Thanks Rajkumar,
When using implicit linking, to use the function exported by DLL, is there any way to use by ordinal other than use by name?
regards,
George
|
|
|
|
|
I think u got confused,
simply using implicit linking by dllexport keyword uses ordinals,
u can use DEF files while using implicit linking to give a constant ordinals inplace of automatically generated ordinals.
|
|
|
|
|
Thanks Rajkumar,
Rajkumar R wrote: u can use DEF files while using implicit linking to give a constant ordinals inplace of automatically generated ordinals.
It is for DLL provider. My question is, could DLL comsumer use ordinal to invoke function exported by DLL other than by name, for example providing ordinal as input parameter?
regards,
George
|
|
|
|
|
I don't want to trace the post that u have posted and CPallini had replied that using GetProcAddress u can pass the ordinals, i think u have no doubts in this,
And in implicit linking, export library take care of linking, u just want to link to the export library. And as we discussed export library uses ordinals, normally automatically generated ordinals, so u don't know the ordinal to call it, and if u still want implicit linking(then calling by GetProcAddress is called explicit linking)and use call by ordinal u need to set ordinals by using DEF files(as u mentioned DLL provider) so that u know the ordinals(linker don't use the generated ordinal)u can call it.
I mentioned DEF files because then only u know the exact ordinal as by default linker generates.
modified on Tuesday, February 12, 2008 4:25 AM
|
|
|
|
|
Thanks Rajkumar,
I think my question should be answered. Let me summarize your points,
1. To use implicit linking, we can assign ordinal by using .DEF files, but for DLL consumer, it has to invoke DLL exported function by name other than by ordinal;
2. To use dynamic loading, i.e. GetProcAddres, as DLL provider, we can not only assign ordinal by using .DEF files, but also as DLL consumer provide ordinal as input parameter.
My understanding correct?
regards,
George
|
|
|
|
|
|
Cool, Rajkumar! Great!!
A question about http://msdn2.microsoft.com/en-us/library/aa271769(VS.60).aspx[^],
Seem if we do not use dllimport there will be one more level of indirection and the root cause is we do not know the address of function from IAT if we do not use dllimport, right?
What is the obstacle of blocking the approach (not using dllimport) from knowing the function address in IAT? From the MSDN, I can not see why if we use dllimport, the IAT can be known and if we do not use IAT the address is not known.
I think the IAT is contained in the import library file (.lib file), and whether or not we are using dllimport, it is input to linker, right (so it is always known)?
regards,
George
|
|
|
|
|
|
Thanks Rajkumar!
regards,
George
|
|
|
|
|
Importing by ordinal is faster as it simply uses the ordinal as an index into an array of function pointers (well RVAs actually) instead of performing a binary search on function names. That said, I doubt that importing by name is a problem for many applications.
Steve
|
|
|
|
|
Thanks Steve,
My question is answered.
regards,
George
|
|
|
|
|
Hello everyone,
I think there is only one COM CreateInstance method, which belongs to IClassFactory interface.
Is there another CreateInstance method, which does not belongs to any class/interface and belongs to the COM global library function (like CoCreateInstance)?
thanks in advance,
George
|
|
|
|
|
Sorry?
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
[my articles]
|
|
|
|
|
Sorry for what? I have not made myself understood, CPallini?
regards,
George
|
|
|
|
|
George_George wrote: I have not made myself understood, CPallini?
Yes. At least I cannot undersatnd what you're asking for.
As you already know CoCreateInstance is simply a shortcut for the sequence
CoGetClassObject(rclsid, dwClsContext, NULL, IID_IClassFactory, &pCF);
hresult = pCF->CreateInstance(pUnkOuter, riid, ppvObj)
pCF->Release();
That, in turn, shows CoGetClassObject, another function of the COM library.
Bottom line, COM library provide a set of standard functions (such as CoInitialize, CoCreateInstance, ...). Does that make you wonder?
If the Lord God Almighty had consulted me before embarking upon the Creation, I would have recommended something simpler.
-- Alfonso the Wise, 13th Century King of Castile.
This is going on my arrogant assumptions. You may have a superb reason why I'm completely wrong.
-- Iain Clarke
|
|
|
|
|
Thanks CPallini,
My question is, for COM defined functions (including the functions in COM defined interface and class) -- which are not used defined functions, beyond the CreateInstance function in IClassFactory, are there another function which has exact the same name of CreateInstance?
Let me know if I have not made myself understood.
regards,
George
|
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
