Re: MSG_MORE socket.h flag

2023-04-04 Thread Chance via Cygwin
On 2023-04-03 04:56, Corinna Vinschen via Cygwin wrote: > On Apr 2 00:19, Chance via Cygwin wrote: >> I've used cygwin in the past few years using the MSG_MORE flag when using >> some socket functions > > I have no idea how you did that. MSG_MORE was never actually supported > by Cygwin, and the

Re: MSG_MORE socket.h flag

2023-04-03 Thread Brian Inglis via Cygwin
On 2023-04-03 04:56, Corinna Vinschen via Cygwin wrote: On Apr 2 00:19, Chance via Cygwin wrote: I've used cygwin in the past few years using the MSG_MORE flag when using some socket functions I have no idea how you did that. MSG_MORE was never actually supported by Cygwin, and the (more or

Re: MSG_MORE socket.h flag

2023-04-03 Thread Corinna Vinschen via Cygwin
On Apr 2 00:19, Chance via Cygwin wrote: > I've used cygwin in the past few years using the MSG_MORE flag when using > some socket functions I have no idea how you did that. MSG_MORE was never actually supported by Cygwin, and the (more or less) equivalent MSG_PARTIAL flag was never exposed into

MSG_MORE socket.h flag

2023-04-01 Thread Chance via Cygwin
I've used cygwin in the past few years using the MSG_MORE flag when using some socket functions but now it's not defined in cygwin\socket.h and MSG_EOR is using the value of MSG_MORE (0x8000). Above that in the socket.h file there is a comment /* MSG_EOR is not supported. We use the MSG_PARTIAL fl