organization of DLL linked functions
Posted
by
m25
on Programmers
See other posts from Programmers
or by m25
Published on 2014-06-09T15:24:26Z
Indexed on
2014/06/09
15:40 UTC
Read the original article
Hit count: 279
So this is a code organization question. I got my basic code working but when I expand it will be terrible. I have a DLL that I don't have a .lib for. Therefore I have to use the whole loadLibrary()/getprocaddress() combo. it works great. But this DLL that i'm referencing at 100+ functions. my current process is (1) typedef a type for the function. or typedef short(_stdcall *type1)(void);
then (2) assign a function name that I want to use such as type1 function_1
, then (3) I do the whole LoadLibrary, then do something like function_1 = (type1)GetProcAddress(hinstLib, "_mangled_funcName@5");
normally I would like to do all of my function definitions in a header file but because I have to do use the load library function, its not that easy. the code will be a mess. Right now i'm doing (1) and (2) in a header file and was considering making a function in another .cpp file to do the load library and dump all of the (3)'s in there. I considered using a namespace for the functions so I can use them in the main function and not have to pass over to the other function.
Any other tips on how to organize this code to where it is readable and organized? My goals are to be able to use function_1
as a regular function in the main code. if I have to a ref::function_1 that would be okay but I would prefer to avoid it. this code for all practical purposes is just plane C at the moment. thanks in advance for any advice!
© Programmers or respective owner