Sujet : Re: best approach for multithreading (?)
De : chris.m.thomasson.1 (at) *nospam* gmail.com (Chris M. Thomasson)
Groupes : comp.lang.cDate : 07. Dec 2024, 07:37:18
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vj0qet$2tv4g$1@dont-email.me>
References : 1 2 3 4 5 6 7 8 9 10
User-Agent : Mozilla Thunderbird
On 12/6/2024 9:16 PM, James Kuyper wrote:
On 12/6/24 11:10, Scott Lurndal wrote:
Kaz Kylheku <643-408-1753@kylheku.com> writes:
On 2024-12-06, James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
...
C <threads.h> can be implemented as a thin wrapper over POSIX threads.
The waste is relatively negligible. The differences, were intended to
allow <threads.h> to also be implemented on non-POSIX systems as
wrappers for whatever the native threading system was.
>
Generally speaking, you can have a function called pthread_create on
non-POSIX systems, and a header <pthread.h>.
>
There are certain requirements of a posix threads implementation that
might be impossible for a non-POSIX system to implement efficiently;
windows, for example, doesn't support signals.
My words above not-withstanding, I am not in any sense an expert on any
kind of threading, nor of Windows. What does POSIX require of threads
with regards to signals?
Well, think of a signal safe function vs one that is not.
best approach for multithreading (?)
Re: best approach for multithreading (?)