Re: best approach for multithreading (?)

On 2024-12-06, Scott Lurndal <scott@slp53.sl.home> wrote:

Kaz Kylheku <643-408-1753@kylheku.com> writes:

On 2024-12-06, James Kuyper <jameskuyper@alumni.caltech.edu> wrote:

On 12/3/24 12:48, Kaz Kylheku wrote:
...

Think about it. The POSIX standard includes ISO C by reference.
So that means POSIX has to have two thread libraries.
It's a waste of flash in embedded systems.

>
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.

It's better to remove requirements from the POSIX standard to implement
a useful subset of POSIX threads, than to remove requirements from POSIX
threads and then change all the names to ISO C threads, to create a
redundant specification.

--
TXR Programming Language: http://nongnu.org/txr
Cygnal: Cygwin Native Application Library: http://kylheku.com/cygnal
Mastodon: @Kazinator@mstdn.ca