Re: [Mingw-users] windows.h dependency

[NightStrike <nightstrike@xxxxxxxxx>]

On 1/30/08, Dave Korn <dave.korn@xxxxxxxxxx> wrote:
> On 30 January 2008 08:49, Vincent Torri wrote:
>
> > On Tue, 29 Jan 2008, NightStrike wrote:
> >
> >> Is it required that every program #include <windows.h> before using
> >> most of the mingw headers?
> >
> > Not always. See msdn. For example, when using sockets, you lay just need
> > winsock2.h
> >
>
>  Well, that's because winsock2.h #includes windows.h anyway, pretty much
> first thing it does.

winsock2 does, but many headers that depend on windows.h do not
themselves include it.  Why does winsock include windows.h but others
do not?  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?

-------------------------------------------------------------------------
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