From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: bug: cygwin-devel v3.0.2-1 socket.h does not #define MSG_EOR per the POSIX standard
Date: Thu, 25 Apr 2019 18:36:00 -0000 [thread overview]
Message-ID: <e6e225d2-2828-a539-6632-76271d0154ed@t-online.de> (raw)
In-Reply-To: <f3ff4eb7-0490-3b53-e45d-9145e7a932c3@redhat.com>
Am 25.04.2019 um 17:48 schrieb Eric Blake:
> On 4/25/19 10:28 AM, Brian Inglis wrote:
>> Would it be allowed and valid to #define MSG_EOR 0 to simplify lack of support?
>
> No, because that implies that EVERY send() call is requesting MSG_EOR
> and that it never fails.
And maybe more importantly, it's explicitly required to be non-zero.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2019-04-25 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-24 15:48 Brabant, Edward H CTR (USA)
2019-04-24 16:44 ` Corinna Vinschen
2019-04-24 17:54 ` Eliot Moss
2019-04-24 20:36 ` Hans-Bernhard Bröker
2019-04-24 20:50 ` Eric Blake
2019-04-25 15:28 ` Brian Inglis
2019-04-25 15:48 ` Eric Blake
2019-04-25 18:36 ` Hans-Bernhard Bröker [this message]
2019-04-25 17:08 ` Corinna Vinschen
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=e6e225d2-2828-a539-6632-76271d0154ed@t-online.de \
--to=hbbroeker@t-online.de \
--cc=cygwin@cygwin.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).