c++ - Reverse header files / linking -

I have some beginner questions about C ++, I have downloaded Windows SDK and as per the documentation, all Bluetooth The use of traffic includes header files in winsock Windows SDK (.h) if I want to program a Bluetooth interface.

a) This is a normal C ++ question: How is the header file winsock.h connected to a specific DLL? I have not specified any links How can I identify all the .dll associated with this header? Header file seems to include only the name of the work and the actual implementation in the DLL? I'm a little confused.

My second goal is to modify the window winsock function by a modified version. I would like to keep the original functionality, unless a flag set by another application is set to true. In this case, I want to modify some functions. My approach is to create a new DLL, which will have the same function name, as the header file is shown in winsock.h.

b) Let's assume that a function fff exists in the original winsock. I will replace it with a new function, unless the flag is not true, the same function calls on FF, but in the unrelated DLL, i mean "inclusion" in the original, "inclusion" and the original function " Overload "My modified FFF function with the original FFF function is the same parameter and the same name in this two functions. How do i do this Is there a better way of achieving the same goal?

c) To be accessible within DLL, what is the best method (or easy way) to allow the flag set by an application?

d) Winsack is a very central component. Do I expect a big performance drop if I add one to each event in it?

a) The header file simply defines things (type, function , Classes) that are going to be found elsewhere - where it does not specify when you link to the program in which. Lib files are included (among other things) Connection of the correct DLL when the program runs Open Code, it loads the DLL into memory and can connect it.

b) Generate another DLL in which all the same functions are included, but together with added (say) ELI_ is added to start the function name then look at the flag inside the ELII function and If he does not call the original winsock function, otherwise do something special that you have.

c) Create a global stable variable in your ELI_LL variable code DLL code, then add additional work to set the flag (and read its status back).

D ) I do not know, but do not take too much time if one does not take too much time. I'm getting more worried about your special code.