From: Norton Allen <allen@huarp.harvard.edu>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: Re: Setting termios VMIN > 0 and VTIME > 0 on non blocking file
Date: Wed, 11 Mar 2020 21:01:34 -0400 [thread overview]
Message-ID: <da57d6cd-b048-8906-1346-d62a5e519d86@huarp.harvard.edu> (raw)
In-Reply-To: <5be321d9-10c2-0853-b716-2abd10a4db3a@SystematicSw.ab.ca>
On 3/11/2020 5:55 PM, Brian Inglis wrote:
> VMIN > 0 || VTIME > 0 implies blocking; O_NONBLOCK implies SIGIO delivery; see:
While I agree with everything else you said there, I don't believe
either of these are true, unless by 'implies' you mean that's how you
usually do it. I have done a lot of work with non-zero VMIN and/or VTIME
in non-blocking situations, and I've done non-blocking with different
approaches to delivery.
--
=============================================================
Norton Allen (he/him/his)
Software Engineer
Harvard University School of Engineering and Applied Sciences
12 Oxford St., Link Bldg. (Office 282)
Cambridge, MA 02138
Phone: (617) 998-5553
=============================================================
next prev parent reply other threads:[~2020-03-12 1:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.1473.1583981776.15804.cygwin@cygwin.com>
2020-03-11 20:48 ` Åke Rehnman
2020-03-11 21:55 ` Brian Inglis
2020-03-12 1:01 ` Norton Allen [this message]
2020-03-12 1:04 ` Åke Rehnman
2020-03-12 1:08 ` Norton Allen
2020-03-12 1:39 ` Åke Rehnman
2020-03-12 8:05 ` Thomas Dickey
2020-03-12 11:01 ` Åke Rehnman
2020-03-12 19:48 ` Achim Gratz
2020-03-12 11:40 ` Corinna Vinschen
2020-03-12 13:32 ` Åke Rehnman
2020-03-12 14:13 ` Corinna Vinschen
2020-03-12 16:42 ` Åke Rehnman
2020-03-13 10:02 ` Corinna Vinschen
2020-03-12 14:20 ` Åke Rehnman
2020-03-12 14:44 ` Corinna Vinschen
2020-03-12 15:08 ` Corinna Vinschen
2020-03-12 17:04 ` Åke Rehnman
2020-03-13 10:12 ` Corinna Vinschen
2020-03-14 10:23 ` Åke Rehnman
2020-03-14 10:36 ` Åke Rehnman
2020-03-16 9:35 ` Corinna Vinschen
2020-03-17 12:16 ` Corinna Vinschen
2020-03-17 15:54 ` Åke Rehnman
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=da57d6cd-b048-8906-1346-d62a5e519d86@huarp.harvard.edu \
--to=allen@huarp.harvard.edu \
--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).