Sujet : Re: OT: Windows (Was: Re: Open Source does not mean easily
De : nicolas$george (at) *nospam* salle-s.org (Nicolas George)
Groupes : comp.unix.programmerDate : 08. Jan 2025, 15:01:07
Autres entêtes
Organisation : Guest of ProXad - France
Message-ID : <677e8523$0$28061$426a34cc@news.free.fr>
References : 1 2 3 4 5
User-Agent : Flrn (0.9.20070704)
Dan Cross, dans le message <
vllql7$sn6$2@reader2.panix.com>, a écrit :
I think it's important to define what you mean when you write,
"thread condition." What, exactly, is that? Perhaps you mean
a condition variable?
Yes, of course that is what “thread condition” means in the context of a
discussion about POSIX threads.
If so, that's true, but I fail to see
the relevance: people write multithreaded code that does IO in
multiple all the time; there are some techniques that are common
for this (Scott alluded to the so-called "pipe trick", due to
Bernstein) and some that are less common.
Yes: there are some techniques that are common to implement I/O concurrency
and that work in the context of threads. You are arguing my point for me:
the threads did not make implementing the I/O concurrency simpler; quite the
opposite it they made them harder, as proven by the fact that “techniques”
had to be deployed.
POSIX threads do not make I/O concurrency easier, they are not made for
that, they are for performance.