Printable View
Hi, recently ive been trying to find out the differences between the windows api (the dll files) and the windows.h header file, i found that the windows.h file contains the declarations and the dll files contain the definitions.
Could you explain to me why this is done in two different files, why not just have the definition and declaration in one file, wouldnt it be less hassle?
they could then Microsoft would have to reveal the source code , which they do not want to do think of it as driving a car , you interact with it , via steering , brakes , gears however common people have no idea what is going on inside , same with API , headers files allow you to use given set of libraries without knowing anything about them ,
It helps developers in what the want to do rather than how they will do it. Perfect example is DirectX or OpenGL , developers want to devepol games they are not interested in how it interacts with underlying video cards.
Thanks for the reply :)
Ive also been trying to find out what actually is the Windows API, is it the windows.h file or the dll files, or a compilation of both which form it?
API
Viggy
Already seen that :)
You have to distinguish between (Windows) API and (Windows) SDK.
By short:
- Windows API (application programming interface) is the set of functions exposed by Windows system libraries (kernel32.dll, user32.dll, etc). API allows other applications to interact with the Windows system.
- Windows SDK (software development kit) contains source header files, static libraries, tools, documentation. SDK helps developers to write applications which are using Windows API to interact with the Windows system.
Windows.h is a source header file shipped with Windows SDK.
Ok, so the dll files form the windows api, and the windows.h file is a part of the windows sdk.
Is the windows sdk automatically provided for us by the IDE when we choose to create a windows application?
It depends on the IDE.Quote:
Originally Posted by TpOreilly
Ok, im guessing mine does, I use MS Visual Studio.
Carrying on from this, couldnt they have both the declarations and the definitions in the dll files?Quote:
Originally Posted by aamir121a
If declarations is in dll files how do you know the function names ?.Quote:
declarations and the definitions in the dll files.
dll files are just like compiled source file, the form is .dll instead of .cpp
First you need to understand why dll files are being written and also find out the answer of function declaration and definition.
I would compare a DLL with an EXE (or LIB), not a CPP file. A DLL is compiled code, all ready to run.Quote:
Originally Posted by hypheni
Viggy
yes you are right Viggy. dll is compiled code ready to run by an exe.
by calling the function names from exe a dll can execute its task, may be missed some term to explain OP exactly.
Ok :) so to summarise and closeee this thread:
The windows.h file contains the declarations and the dll files contain the definitions of the functions within the windows API.
They seperate the declarations from the definitions because they dont want people to know how the functions actually work.
And the dll files are the windows api, and the windows.h file is a part of the windows sdk.
Correct me if im wrong.
a dll is like an exe, but it is not a stand alone application and is meant to be loaded inside a process. It runs inside a thread attached to your process. It is to provide implementations dynamically vs statically. Instead of being compiled together, they link together during runtime. a dll is a format that the os uses to provide dynamic linking. I suggest you read http://en.wikipedia.org/wiki/Dynamic...on_and_binding.
It is not to hide code. You don't need the c/c++ source, but only a compiled( assembly machine code ) version in a specific format that the os can use. This is why dlls are needed. It has to do with loading up dependencies at run-time or during exe loading.