Daishi, Personally, I would recommend implementing inet_ntop and inet_pton on Windows. The lack of those functions is, IMO, broken. I looked at the code in the mailing archive and it looks totally generic---like it came right out of a UNIX libc. So, if the author says the license is BSD-incompatible, you can probably find equivalent code easily.
Eventually it might be good to take some of the networking utilities out of tcp, udp, hostinfo etc. and combine it into a network utility egg (or include file), if possible. Some of the functionality in these is duplicated. This might include the Windows versions of inet_ntop and inet_pton. Even the high-level ip->string and string->ip conversions seem a bit out of place in hostinfo, to me. If you need to make a setup file, feel free to create an egg. I don't mind if you send it directly to Felix or commit it, just copy me. On 11/21/05, Daishi Kato <[EMAIL PROTECTED]> wrote: > Hi, > > Thanks for the pointer. > The answer is that inet_ntop is not available on winsock2. > > Which would you suggest, > to use the code in the mail archive, (not sure > if it is allowed to reuse it by the license) > or just to use inet_ntoa instead and does not support IPv6? > > It is currently not easy to send you a patch, > because the egg is single scm file, which does not > include hostinfo.setup. Would you update it so that > the egg will be hostinfo.egg, or I could do it. > > Daishi > > At Fri, 18 Nov 2005 12:12:14 -0600, > Zbigniew wrote: > > > > This might answer your question: > > http://www.mail-archive.com/users@ipv6.org/msg02107.html _______________________________________________ Chicken-users mailing list Chicken-users@nongnu.org http://lists.nongnu.org/mailman/listinfo/chicken-users
