Re:Include-what-you-use: Clang tool to analyze includes in C...
by maxlybbert on Saturday January 23, 2016 @11:26AM
(#10958836)
The obvious one would be #include <windows.h>. I have never checked to see how big that file actually is, but it's not anywhere near what you would think based on what functions MSDN says need you to #include it for. The truth is, it #includes several other files, because Microsoft, in its infinite wisdom decided that, for the most part, programmers don't have to know what file a declaration is actually in, they just need to remember #include <windows.h>.
[ Parent
| on HN ]
There are no comments on this comment yet.