Subject: Threads and processes (was: Re: "The end of software secrecy is almost upon)
On 2026-10-25,
boltar@caprica.universe wrote:
On Sun, 25 Oct 2026 13:34:58 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
[snip]
No, it isn't. How similar do you think the posix and windows threading >>>model/api are? Yet somehow C++ provides a common wrapper for both. There is >>>no reason the same can't be done for processes and your irrelevant waffle >>>about past issues of threading on *nix don't change that.
You didn't answer my questions.
What do you think that a "thread" is?
What do you think that a "process" is?
Stop playing games - you don't get to answer a question with a question. Given I've been programming on unix for over 30 years and have written dozens of applications using multi process and multi threading and sometimes using both
I'm quite well aware of the differences. Perhaps you arn't which is why you need me to tell you. Well go do your own research.
In the meantime I'll ask one last time - why do you think C++ can provide
a threading wrapper API but not a multi process one?
Take your time.
It tends to be somewhat easy to get lost in misunderstandings even when
using the very same language. So, if you're discussing threads and/or processes, explaining what do you mean by these two concepts at least
ensures there's one less source of potential misunderstandings. With
that in account, it's less than stellar not to answer. And then kind of
pulling rank to do so...
"Le langage est source de malentendus." -- Saint-ExupŠry
--
Nuno Silva
--- PyGate Linux v1.5.19
* Origin: Dragon's Lair, PyGate NNTP<>Fido Gate (3:633/10)