On Sat, Mar 24, 2012 at 11:48:18AM +0100, Eugen Dedu wrote: > On 24/03/12 10:41, Stephen Kitt wrote: > >On Fri, 23 Mar 2012 10:07:05 +0100, Eugen Dedu > ><eugen.d...@pu-pm.univ-fcomte.fr> wrote: > >>Stephen, where do you check if a header needs to have another header > >>included (such as windows.h)? > >> > >>I have found a very interesting thread: > >>http://old.nabble.com/windows.h-dependency-td15175386.html > > > >It is very interesting indeed. As far as I know the way to check whether > >another header is needed it to look up the documentation on MSDN, although it > >does tend to be incomplete — for instance the documentation for DNS functions > >only mentions windns.h, even though windns.h needs windows.h (or more > >typically, winsock2.h). In general, if a header doesn't build on its own, > >adding windows.h before it fixes things. > > Indeed, but we try to be as close to Windows as possible, so if on > Windows it does not require windows.h, then with mingw it should not > either.
My statement regarding windns.h and its use with winsock2.h was based on my Windows development experience, not on tests with MinGW-w64. As mentioned on for #661444, I've checked windns.h using Visual C++ 2010 as well as MinGW-w64 and it does still require windows.h or winsock2.h. Regards, Stephen -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org