[Frank Lhota points out many of the evils of Winsock on Windows, which is not needed when using Cygwin]
Frank, I am looking forward to adding your Cygwin configuration for Unicon, and of course, you will need to add what #ifdef's you have to in order for it to use regular sockets and not Winsock. I am not interested in defending Winsock, but it has been made to work, more or less successfully, by many many Windows applications, and Unicon's implementation has taken care of most of the differences and problems you note between Winsock and UNIX sockets. Since many Windows users will not choose to install an entire UNIX emulation package (Cygwin) on top of their Windows in order to run Unicon, I don't see the native Windows configurations going away anytime soon, so the Winsock code will remain in place, under appropriate #ifdef's, for the forseeable future. Frank, unless you are telling me that Mingw32, the Minimum GCC for Win32, has real sockets available, I don't see that you can demand that the NTGCC configuration may not use Winsock. The most you can reasonably argue is that under the NTGCC umbrella we need separate CYGWIN and MINGW32 #ifdef's, with CYGWIN using more of the UNIX code, and MINGW32 using more of the regular (i.e. MS Windows, Visual C++) code. I am very fine with you adding these #ifdef's, and I maybe able to help some. Clint [EMAIL PROTECTED] ------------------------------------------------------- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 _______________________________________________ Unicon-group mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unicon-group
