Jan Echternach wrote: > > On Wed, Nov 15, 2000 at 10:10:43PM -0800, Mark Wedel wrote: > > When using sendto, you are not required to actually have a socket connected. > > So using O_NONBLOCK may not do anything. > > O_NONBLOCK is a socket property, not a connection property. It is > supposed to work, at least according to SUSv2. At least on my linux box, the defined value for O_NONBLOCK is different than the defined value for MSG_DONTWAIT. But perhaps an #ifdnef MSG_DONTWAIT/define MSG_DONTWAIT O_NONBLOCK/#endif is the best way to handle that. > > -- > Jan > _______________________________________________ > crossfire-devel mailing list > crossfire-devel at lists.real-time.com > https://mailman.real-time.com/mailman/listinfo/crossfire-devel