Re: best approach for multithreading (?)

On 12/3/2024 9:48 AM, Kaz Kylheku wrote:

On 2024-12-01, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

On 12/1/2024 7:54 AM, Kaz Kylheku wrote:

On 2024-12-01, Lew Pitcher <lew.pitcher@digitalfreehold.ca> wrote:

On Sun, 01 Dec 2024 15:10:03 +0000, candycanearter07 wrote:

There's a standard library for multithreading.
https://www.man7.org/linux/man-pages/man7/pthreads.7.html

>
Since C11, the C standard library has provided it's own support for
threading, which (I'm told) closely resembles the POSIX threading
model implemented in the Linux pthreads library.

>
Yes; they stupidly took a chunk of POSIX (IEE 1003 standard, originally
formed as a fork of C to standarize Unix things) and cloned an
incompatible version with different types and function names.
>
For over a decade before that, people were already using POSIX threads
on platforms that don't have POSIX threads, via libraries.

>
Here is one I used to always use back in the day over on Windows:
>
https://sourceware.org/pthreads-win32/

 And that is not significantly harder to implement (if at all) than C11
threading.

Back then, iirc, it was "hard", or "tricky" to create a compliant condition variable on windows. There were a lot of tries, but 90% of them had issues. Some of them only supported SCHED_OTHER, and others would seem to work until they deadlocked. Missing waiter thing. God, its been a while! Way back in very early 2000's for me.

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.

POSIX needs a whole system to be compliant (compiler, ect...). I remember an old post over on c.p.t where, iirc, GCC broke this contract wrt a pthread_mutex_trylock(). I wonder if I can still find that damn thread! I posted in it and so did Dave Butenhof.