On Jun 29 12:03, Kai Tietz wrote: > 2012/6/28 Corinna Vinschen <vinsc...@redhat.com>: > > So, are you proposing to include cygwin/in6.h from in6addr.h or > > winsock2.h? What would be the advantage? You'd still need to guard > > these includes with __INSIDE_CYGWIN__ and you'd still have to disable > > the winsock2.h definitions the same way. > > Right. I am just a fan of having dependencies resolved in place. > Means winsock header defines normally in6_addr, so why not do this > here too. By this you avoid implicit dependencies.
Well, in theory a Cygwin application should use winsock *or* POSIX sockets. Mixing the headers is not supported on the application level. Only Cygwin itself is supposed to do that to implement POSIX sockets with winsock functions. I would actually not really like to see this mix be used outside of Cygwin at all. > Well, the usage of __INSIDE_CYGWIN__ might be a bit random, but of > more importance for now is, that things remain consistent. The chance > to clean it up a bit - if possible - we have later on, too. > > So please go ahead with that patch. Thanks, will do. Corinna ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Mingw-w64-public mailing list Mingw-w64-public@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mingw-w64-public
