You never know what stuff the standard headers might include. But it does not matter either. You included the correct header to use what you needed, and that's all we really need to know.
Different implementations of the standard library might have a different include pattern.
Originally Posted by Adak
Ok, I thought it might had something to do with the size of the executable file after building it if there where more header files included.
The size of your executable depends largely on the fact that's it's a debug build. It contains a lot of debug information / code and isn't really optimized.
When you ship your program to someone else, you choose a Release build. It will be much smaller, I assure you.
They do supply basic information that allows you to get correct stack traces through their DLLs. You just have to add their official debug information server to your list.But Microsoft does not ship debug information for system files such as ntdll.dll.
All the buzzt!
CornedBee
"There is not now, nor has there ever been, nor will there ever be, any programming language in which it is the least bit difficult to write bad code."
- Flon's Law
Indeed they do. I sort of avoided mentioning that. But you're right. However, they don't ship with VS nor the OS. You'll have to download the debug symbols either from a symbol server or manually from MS's servers.
To the both of you. Could you explain how it is done what you mentioned?
I know I am probably becoming a pain in the ass with all my stupid questions but yeah, trying to learn hey....
Tools -> Options -> Debugging -> Symbols.
Select Microsoft's symbol server. Select local cache. Tinker with the settings, if you will.
Then select OK.
The IDE will not download debug info for Microsoft DLLs (may take some time to download, though).
