Derek Price wrote: >That's exactly what the NO_SOCKET_TO_FD #definition is for and that's >why the socket-client.c file is necessary in the first place. Probably >someone (likely me) added a call that assumes a socket descriptor may be >treated like a file descriptor and neglected to use the #ifdef >NO_SOCKET_TO_FD switch to select socket_buffer_initialize instead of >fd_buffer_initialize. Can you figure out where the buffer came from? > >
Sorry, I had that last reversed. Is there some way to find out if a file descriptor is ready for read or write in Windows, other than select? Regards, Derek -- Derek R. Price CVS Solutions Architect Ximbiot <http://ximbiot.com> v: +1 717.579.6168 f: +1 717.234.3125 <mailto:[EMAIL PROTECTED]> _______________________________________________ Bug-cvs mailing list [email protected] http://lists.nongnu.org/mailman/listinfo/bug-cvs
