From: Keith M. <kei...@us...> - 2008-02-02 16:42:54
|
On Saturday 02 February 2008 15:37, NightStrike wrote: > I would think that a user should only include windows.h if > his own code requires it, not if a library he is using requires it. > That library should handle its own dependencies, yes? Yes. What possible benefit can be gained from #including *any* header, if your compilation unit has no direct dependency on it? This isn't peculiar to windows.h; it applies equally to every header. Regards, Keith. |