From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: Chance <exertustfm@gmail.com>
Cc: cygwin@cygwin.com
Subject: Re: MSG_MORE socket.h flag
Date: Mon, 3 Apr 2023 12:56:48 +0200 [thread overview]
Message-ID: <ZCqw8BFY0XQhvG7D@calimero.vinschen.de> (raw)
In-Reply-To: <CACq6C22yVYO9HPV+GYOJ6X0WACsjNKcjg82k0QTFp9v380+WQw@mail.gmail.com>
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 Cygwin user space.
> but now it's not defined in cygwin\socket.h and
It never was! I checked the history back until the year 2000.
> 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 flag here */. I understand this as meaning MSG_EOR now works as
> MSG_MORE would and that MSG_EOR is not usable. Just want some clarification
> on this.
It just means we're using the bit value of MSG_PARTIAL to expose
a MSG_EOR flag into user space. It was introduced in 2019 because
of POSIX header file compatibility, but it's unsupported and always
results in sedn/recv returning EOPNOTSUPP.
I'm still puzzled where you got the MSG_MORE definition from, though.
Corinna
next prev parent reply other threads:[~2023-04-03 10:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 5:19 Chance
2023-04-03 10:56 ` Corinna Vinschen [this message]
2023-04-03 16:05 ` Brian Inglis
2023-04-04 11:24 ` Chance
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZCqw8BFY0XQhvG7D@calimero.vinschen.de \
--to=corinna-cygwin@cygwin.com \
--cc=cygwin@cygwin.com \
--cc=exertustfm@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).