On Fri, Jul 21, 2006 at 11:40:22AM +0200, Corinna Vinschen wrote: > > Just as a side note to Jan. Cygwin is a Red Hat product as well and the > current release doesn't support IPv6 and getaddrinfo for now. I have a > developer branch which adds IPv6 support to Cygwin, but this work will > hit the streets only in a few weeks or months. > > Of course I wouldn't like to see OpenSSL suddenly breaking on current > version of Cygwin just because IPv6 (resp. getaddrinfo) is used > unconditionally ;-)
The getaddrinfo patch was showing a code to get IPv6 support in there, in a way that was IPv4-compatible with platforms that have getaddrinfo. I never said that it should be used unconditionally. I didn't put the conditions there because it makes it easier to see and review _the new code_. Once there is agreement that in order to support IPv6, the code path should look like outlined, no problem adding proper conditioning, be it compile-time or run-time one. Why is the main focus being put on the conditioning part, not on the core of the patch? Having said that, implementing getaddrinfo and freeaddrinfo as a simple wrapper around gethostbyname (et family) for sockaddr_in-only plaforms and leaving the main code free from #ifdefs and other conditions might be more appealing to me, but again -- the patch tried to address the IPv6 issue first. -- Jan Pazdziora ______________________________________________________________________ OpenSSL Project http://www.openssl.org Development Mailing List [email protected] Automated List Manager [EMAIL PROTECTED]
