From: Ken Brown <kbrown@cornell.edu>
To: cygwin-devel <cygwin-developers@cygwin.com>
Subject: Question about non-blocking Windows pipes
Date: Thu, 1 Apr 2021 10:39:23 -0400 [thread overview]
Message-ID: <d670ecbe-7270-03bb-c2ea-cc34d5e1bca5@cornell.edu> (raw)
Hi Corinna,
There are several places in fhandler_socket_unix.cc where you make a distinction
between the blocking and nonblocking cases with code like this:
cygwait (evt ?: get_handle (),...)
Here evt is an event handle in the blocking case and is NULL in the nonblocking
case. See, for example, fhandler_socket_unix::listen_pipe.
What's the reasoning behind this? Why not just always create an event or always
use the handle? I guess I don't understand what Windows does differently in the
two cases.
Thanks.
Ken
next reply other threads:[~2021-04-01 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-01 14:39 Ken Brown [this message]
2021-04-06 12:57 ` Corinna Vinschen
2021-04-06 13:33 ` Ken Brown
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=d670ecbe-7270-03bb-c2ea-cc34d5e1bca5@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin-developers@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).