In article <7gb1N.177699$[email protected]>,
Scott Lurndal <[email protected]> wrote:

Kaz Kylheku <[email protected]> writes:

On 2023-11-03, Scott Lurndal <[email protected]> wrote:

The introduction of threads pretty much invalidated the idea of
a global errno, which is why all newly defined POSIX system calls
return the error number directly rather than leveraging the
legacy errno (threaded applications define errno as a thread-local
variable to accomodate the legacy system calls).

I hate having to killfile my own thread.

--
The randomly chosen signature file that would have appeared here is more than 4 lines long. As such, it violates one or more Usenet RFCs. In order to remain in compliance with said RFCs, the actual sig can be found at the following URL:
http://user.xmission.com/~gazelle/Sigs/Security

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)

On Friday, November 3, 2023 at 1:23:51 PM UTC-7, Kenny McCormack wrote:

In article <7gb1N.177699$[email protected]>,
Scott Lurndal <[email protected]> wrote:

Kaz Kylheku <[email protected]> writes:

On 2023-11-03, Scott Lurndal <[email protected]> wrote:

The introduction of threads pretty much invalidated the idea of
a global errno, which is why all newly defined POSIX system calls
return the error number directly rather than leveraging the
legacy errno (threaded applications define errno as a thread-local
variable to accomodate the legacy system calls).

I hate having to killfile my own thread.

So you missed the post where Kaz suggested the process would need to make the target tty its controlling tty? That's unfortunate.

Philip Guenther

--- SoupGate-Win32 v1.05
* Origin: fsxNet Usenet Gateway (21:1/5)