Re: [Mingw-users] windows.h dependency
On Sunday 03 February 2008 15:47, NightStrike wrote:
> Every header should be protected against multiple inclusion. If it's
> not, that's a bug.
Technically, yes. However, I consider it to be just as much a bug to
introduce a circular dependency between headers, and subsequently rely
on multiple inclusion guards to pull you out of the mire.
> The point is that dependencies of a header should
> be resolved by the header, and not the user of the header.
This doesn't apply, if the user is using a header improperly. When the
documentation says `defined in foo.h; include windows.h', then it is a
*user* error to `#include <foo.h>'; in this case, foo.h should *not*
`#include <windows.h>', to circumvent such misuse.
Regards,
Keith.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
MinGW-users mailing list
MinGW-users@xxxxxxxxxxxxxxxxxxxxx
You may change your MinGW Account Options or unsubscribe at:
https://lists.sourceforge.net/lists/listinfo/mingw-users