• Re: =?UTF-8?Q?=E2=80=9CThe?= end of software secrecy is almost upon

    From kludge@kludge@panix.com (Scott Dorsey) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 13:47:48 2026
    From Newsgroup: comp.lang.c++

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    Still, somebody had to decide to make the MS-DOS COPY command refuse
    to copy zero-length files - something which CP/M's PIP did happily.

    That's a bug and not a feature. Sometimes you want to have a zero-length
    file in place as a semaphore.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 12:07:45 2026
    From Newsgroup: comp.lang.c++

    Scott Dorsey wrote:
    In article <11bhpo6$2lpjl$1@dont-email.me>, <boltar@caprica.universe> wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
    On 10/23/2026 11:06 AM, Peter Flass wrote:
    Bill Gates never earned a degree. He seemed to do ok.

    From what I understand, he wasn't a very good programmer, though.

    Bill Gates wrote the Microsoft Basic compiler and interpreter for the
    Altair 8080 in 2K of ram using assembly language. Take that as you will. >>
    Gates when he put his mind to it could certainly program. Even Sinclair
    required 4K for BASIC in the ZX80 for example. But some of his technical
    (and business) decisions leave a lot to be desired.

    But the ZX80 (and most later MBASICs) had floating point.
    --scott

    Gates had a guy from Harvard do the math works. He was only with the
    company 10 weeks.
    --
    Can you strip away so we may start again?
    "ThererCOs a switch and they don't
    seem authentic or themselves. It
    feels like IrCOm an unnecessary
    body and itrCOs a waste of time to
    even be there." -- Grim, playful Blaine.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 13:04:38 2026
    From Newsgroup: comp.lang.c++

    On 10/23/2026 8:44 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 23:31:41 GMT, Charlie Gibbs wrote:

    On 2026-10-23, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    What was that error message? I was expecting something like rCLDISK
    ERRORrCY or rCLI/O ERRORrCY. Instead, it said

    IrCOm having trouble with the disk.

    The idea of an error message phrased in plain, approachable
    language (using a first-person pronoun, even) instead of technical
    terms?? That was a revelation.

    Unfortunately it's not the kind of revelation I welcome. Back in my
    mainframe days, I learned to hate catch-all error messages; they're
    the sign of a programmer who's too lazy to try to help the user. If
    something goes wrong, I want to be given some clues as to where to
    look. But more and more these days, your typical error message is
    "Something went wrong." Nothing more. This kind of conduct should be
    condemned.

    This was not like that though, was it? On systems of that era, you
    would typically get something like rCLDISK ERRORrCY or rCLI/O ERRORrCY. The plain-language message was no less specific than that.

    Do you want more detail about what went wrong? Perhaps a CRC
    validation failure? Sector-addressing failure? Missing address/data
    marks? Invalid GCR/RLL encoding?

    That kind of low-level detail might be helpful to somebody (perhaps a hardware engineer) trying to fix the problem. And perhaps it should
    appear in a system log somewhere.

    And it wouldnrCOt have mattered much in this case, anyway, since it
    would have been obvious to anybodyrCi sitting or standing in front of the machine, that the most likely cause was the fact that there was no
    disk in the drive.

    rCiAnybody who had made much use of floppy disks on micros, anyway.

    Iirc, BASIC had a fun error. I cannot remember the damn exact phrase, it
    was something like expression too complex or something.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 21:38:42 2026
    From Newsgroup: comp.lang.c++

    On 2026-10-24, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 10/23/2026 8:44 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 23:31:41 GMT, Charlie Gibbs wrote:

    On 2026-10-23, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    What was that error message? I was expecting something like rCLDISK
    ERRORrCY or rCLI/O ERRORrCY. Instead, it said

    IrCOm having trouble with the disk.

    The idea of an error message phrased in plain, approachable
    language (using a first-person pronoun, even) instead of technical
    terms?? That was a revelation.

    Unfortunately it's not the kind of revelation I welcome. Back in my
    mainframe days, I learned to hate catch-all error messages; they're
    the sign of a programmer who's too lazy to try to help the user. If
    something goes wrong, I want to be given some clues as to where to
    look. But more and more these days, your typical error message is
    "Something went wrong." Nothing more. This kind of conduct should be
    condemned.

    This was not like that though, was it? On systems of that era, you
    would typically get something like rCLDISK ERRORrCY or rCLI/O ERRORrCY. The >> plain-language message was no less specific than that.

    Do you want more detail about what went wrong? Perhaps a CRC
    validation failure? Sector-addressing failure? Missing address/data
    marks? Invalid GCR/RLL encoding?

    That kind of low-level detail might be helpful to somebody (perhaps a
    hardware engineer) trying to fix the problem. And perhaps it should
    appear in a system log somewhere.

    And it wouldnrCOt have mattered much in this case, anyway, since it
    would have been obvious to anybodyrCi sitting or standing in front of the
    machine, that the most likely cause was the fact that there was no
    disk in the drive.

    rCiAnybody who had made much use of floppy disks on micros, anyway.

    Iirc, BASIC had a fun error. I cannot remember the damn exact phrase, it
    was something like expression too complex or something.

    "Who is General Failure and why is he reading my disk?"
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 01:11:51 2026
    From Newsgroup: comp.lang.c++

    On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:

    In article <11bj08r$309uk$1@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/24/26 09:41, Dan Cross wrote:
    In article <11bhppd$2lpkc$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bf4d1$skul$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bd7rg$2cvfs$1@dont-email.me>,
    <boltar@battlestar.co.uk> wrote:

    You need an OS to do threading properly too. Theres a reason
    green threads in java were a joke.

    Weird that you think you need a operating system for threads,
    yet you want C to standardize processes which also ... need an
    operating system. I mean, POSIX already does an ok job of
    standardizing the sorts of process-y things you would expect
    from, you know, an operating system.

    I'm simply pointing out the inconsistency in having a threading
    library but not a process library. Its perfectly possible to
    simulate a multiprocess enviroment.

    So write a simulator in your language of choice. You don't need
    the language to standardize a process model for that.

    Ditto threads. So why does C++ have a threading library?

    Take your time...

    What, pray tell, do you think that a _thread_ is? And how is it
    different from a _process_? For that matter, what do you think
    that a _process_ is?

    Please, take all the time you need to answer.

    Threads share resources such as address space, files, etc. A process
    runs in its own address space. (at least these days, before virtual >memory, who knows?)

    Indeed, but I'm hoping Mr Boltar will chime in with his answers,
    so that we can understand why thinks that a language like C
    should introduce a *process* model, and how threads are similar.

    - Dan C.


    First, he was talking about C++. Unlike me, he does not appear to care
    about C.
    Second, while in theory threads can be implemented by C++
    compilers+language support library, in practice I had never seen it
    done. All I had seen is C++ threads implemented in library as thin
    wrapper atop of the OS (or RT executive) implementation.
    I can not see while the same can't be done for processes, with
    API modeled on posix_spawn() or Windows CreateProcess().
    It does not look like variety in this field is bigger than in case of
    threads. More like it is smaller.

    Now, would it be the first thing I would want like addition to C++
    standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...
















    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 00:28:19 2026
    From Newsgroup: comp.lang.c++

    In article <20261025011151.000038ef@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:

    In article <11bj08r$309uk$1@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/24/26 09:41, Dan Cross wrote:
    In article <11bhppd$2lpkc$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bf4d1$skul$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bd7rg$2cvfs$1@dont-email.me>,
    <boltar@battlestar.co.uk> wrote:

    You need an OS to do threading properly too. Theres a reason
    green threads in java were a joke.

    Weird that you think you need a operating system for threads,
    yet you want C to standardize processes which also ... need an
    operating system. I mean, POSIX already does an ok job of
    standardizing the sorts of process-y things you would expect
    from, you know, an operating system.

    I'm simply pointing out the inconsistency in having a threading
    library but not a process library. Its perfectly possible to
    simulate a multiprocess enviroment.

    So write a simulator in your language of choice. You don't need
    the language to standardize a process model for that.

    Ditto threads. So why does C++ have a threading library?

    Take your time...

    What, pray tell, do you think that a _thread_ is? And how is it
    different from a _process_? For that matter, what do you think
    that a _process_ is?

    Please, take all the time you need to answer.

    Threads share resources such as address space, files, etc. A process
    runs in its own address space. (at least these days, before virtual
    memory, who knows?)

    Indeed, but I'm hoping Mr Boltar will chime in with his answers,
    so that we can understand why thinks that a language like C
    should introduce a *process* model, and how threads are similar.

    - Dan C.


    First, he was talking about C++. Unlike me, he does not appear to care
    about C.

    First, he's a big boy, and I'm sure he can answer for himself.
    But ok then, C++, not C. The questions still stand.

    Second, while in theory threads can be implemented by C++
    compilers+language support library, in practice I had never seen it
    done.

    This is not saying much about anything aside from the countours
    of your own experience, I'm afraid.

    All I had seen is C++ threads implemented in library as thin
    wrapper atop of the OS (or RT executive) implementation.

    In the late 1990s, into the early 2000s, most "threads" on
    Unix-style systems were implemented in userspace, in the C
    library, often by exposing the "normal" system call endpoints
    in the library, but making them thin wrappers around equivalent
    asynchronous system calls.

    There was even a paper about using the Xinu pedagogical system
    from Doug Comer to implement something very close to threads on
    4.2BSD, with signals and a context saving/restoration primitive
    to approximate a timer interrupt.

    For a more recent historical example the FreeBSD MP library was
    initially implemented this way, as were pre-LinuxThreasd threads
    on Linux; Solaris threads up until Solaris 2.6 or so similarly.

    Of course, it wasn't a great way to do things because if
    something _did_ block...well, there went your concurrency.

    Making Unix systems multithreaded was challenging because of
    decades of software that was written assuming a single-threaded
    userspace environment (the kernel had been "multithreaded" since
    very near the start, even if much of the system was written
    assuming a single processor; but parallelism is not the same
    thing as concurrency), and this was compounded because people
    were trying to implement complex M:N threading models; Sun did
    this, and FreeBSD tried with their KSEs; the Linux people did
    not. While cool in theory, M:N threading relied on very
    specific usage patterns to work well in practice, and almost no
    one actually wrote software that way, so you ended up with
    userspace threads fighting the kernel scheeduler, and vice
    versa.

    More recently, the Akaros research system introduced the notion
    of a "many-core process" and pushed fine-grained "thread"
    scheduling entirely to userspace; the kernel is totally unaware
    of how userspace schedules anything. That system uses an N:C
    model, where $C$ is the number of *cores* assigned to a process
    (all system calls in Akaros are asychronous by design, to avoid
    the pitfalls of user-threads blocking on synchronous kernel
    services that beset Unix).

    I can not see while the same can't be done for processes, with
    API modeled on posix_spawn() or Windows CreateProcess().

    C, and C++, have had `system()` for as long as I can remember,
    if you just want to run a program (note that both `posix_spawn`
    and `CreateProcess` take the names of programs to run in that
    new process).

    It does not look like variety in this field is bigger than in case of >threads. More like it is smaller.

    Nope. But if you think differently, see the questions above.

    Now, would it be the first thing I would want like addition to C++
    standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...

    POSIX has all of that. POSIX also has a process model. Why not
    just make POSIX a part of the language, then? (Answer that and
    you may start to understand why this is harder than it looks
    for C++ [and C].)

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 08:42:34 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:

    In article <20261025011151.000038ef@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:

    In article <11bj08r$309uk$1@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/24/26 09:41, Dan Cross wrote:
    In article <11bhppd$2lpkc$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bf4d1$skul$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bd7rg$2cvfs$1@dont-email.me>,
    <boltar@battlestar.co.uk> wrote:

    You need an OS to do threading properly too. Theres a
    reason green threads in java were a joke.

    Weird that you think you need a operating system for
    threads, yet you want C to standardize processes which also
    ... need an operating system. I mean, POSIX already does
    an ok job of standardizing the sorts of process-y things
    you would expect from, you know, an operating system.

    I'm simply pointing out the inconsistency in having a
    threading library but not a process library. Its perfectly
    possible to simulate a multiprocess enviroment.

    So write a simulator in your language of choice. You don't
    need the language to standardize a process model for that.

    Ditto threads. So why does C++ have a threading library?

    Take your time...

    What, pray tell, do you think that a _thread_ is? And how is it
    different from a _process_? For that matter, what do you think
    that a _process_ is?

    Please, take all the time you need to answer.

    Threads share resources such as address space, files, etc. A
    process runs in its own address space. (at least these days,
    before virtual memory, who knows?)

    Indeed, but I'm hoping Mr Boltar will chime in with his answers,
    so that we can understand why thinks that a language like C
    should introduce a *process* model, and how threads are similar.

    - Dan C.


    First, he was talking about C++. Unlike me, he does not appear to
    care about C.

    First, he's a big boy, and I'm sure he can answer for himself.
    But ok then, C++, not C. The questions still stand.

    Second, while in theory threads can be implemented by C++ >compilers+language support library, in practice I had never seen it
    done.

    This is not saying much about anything aside from the countours
    of your own experience, I'm afraid.

    All I had seen is C++ threads implemented in library as thin
    wrapper atop of the OS (or RT executive) implementation.

    In the late 1990s, into the early 2000s, most "threads" on
    Unix-style systems were implemented in userspace, in the C
    library, often by exposing the "normal" system call endpoints
    in the library, but making them thin wrappers around equivalent
    asynchronous system calls.

    There was even a paper about using the Xinu pedagogical system
    from Doug Comer to implement something very close to threads on
    4.2BSD, with signals and a context saving/restoration primitive
    to approximate a timer interrupt.

    For a more recent historical example the FreeBSD MP library was
    initially implemented this way, as were pre-LinuxThreasd threads
    on Linux; Solaris threads up until Solaris 2.6 or so similarly.

    Of course, it wasn't a great way to do things because if
    something _did_ block...well, there went your concurrency.

    Making Unix systems multithreaded was challenging because of
    decades of software that was written assuming a single-threaded
    userspace environment (the kernel had been "multithreaded" since
    very near the start, even if much of the system was written
    assuming a single processor; but parallelism is not the same
    thing as concurrency), and this was compounded because people
    were trying to implement complex M:N threading models; Sun did
    this, and FreeBSD tried with their KSEs; the Linux people did
    not. While cool in theory, M:N threading relied on very
    specific usage patterns to work well in practice, and almost no
    one actually wrote software that way, so you ended up with
    userspace threads fighting the kernel scheeduler, and vice
    versa.

    More recently, the Akaros research system introduced the notion
    of a "many-core process" and pushed fine-grained "thread"
    scheduling entirely to userspace; the kernel is totally unaware
    of how userspace schedules anything. That system uses an N:C
    model, where $C$ is the number of *cores* assigned to a process
    (all system calls in Akaros are asychronous by design, to avoid
    the pitfalls of user-threads blocking on synchronous kernel
    services that beset Unix).


    How any of this trivia has anything to do with real-world
    implementations of C++11 threads?

    I can not see while the same can't be done for processes, with
    API modeled on posix_spawn() or Windows CreateProcess().

    C, and C++, have had `system()` for as long as I can remember,
    if you just want to run a program (note that both `posix_spawn`
    and `CreateProcess` take the names of programs to run in that
    new process).


    I mentioned that in one of my earlier responses to boltar.
    However there exist situation in which system() is not a satisfactory replacement for spawn(), most often because overhead of launching shell sometimes matters.

    It does not look like variety in this field is bigger than in case of >threads. More like it is smaller.

    Nope. But if you think differently, see the questions above.

    Now, would it be the first thing I would want like addition to C++
    standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...

    POSIX has all of that. POSIX also has a process model. Why not
    just make POSIX a part of the language, then? (Answer that and
    you may start to understand why this is harder than it looks
    for C++ [and C].)

    - Dan C.


    It (both spawn and IPv4) is not harder (and not easier) than
    fopen/fread/fwrite or than time-related functions.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Ian@${send-direct-email-to-news1021-at-jusme-dot-com-if-you-must}@jusme.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 08:22:10 2026
    From Newsgroup: comp.lang.c++

    On 2026-10-24, Scott Dorsey <kludge@panix.com> wrote:
    In article <11bhpo6$2lpjl$1@dont-email.me>, <boltar@caprica.universe> wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
    On 10/23/2026 11:06 AM, Peter Flass wrote:
    Bill Gates never earned a degree. He seemed to do ok.

    From what I understand, he wasn't a very good programmer, though.

    Bill Gates wrote the Microsoft Basic compiler and interpreter for the >>>Altair 8080 in 2K of ram using assembly language. Take that as you will.

    Gates when he put his mind to it could certainly program. Even Sinclair >>required 4K for BASIC in the ZX80 for example. But some of his technical >>(and business) decisions leave a lot to be desired.

    But the ZX80 (and most later MBASICs) had floating point.
    --scott

    The ZX80 did not have floating point in its stock BASIC ROM. The ZX81 did.
    --
    Ian

    "Tamahome!!!" - "Miaka!!!"
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 08:41:48 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <20261025011151.000038ef@yahoo.com>,
    Now, would it be the first thing I would want like addition to C++
    standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...

    POSIX has all of that. POSIX also has a process model. Why not
    just make POSIX a part of the language, then? (Answer that and
    you may start to understand why this is harder than it looks
    for C++ [and C].)

    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.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 13:32:54 2026
    From Newsgroup: comp.lang.c++

    In article <20261025084234.0000449c@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:
    In article <20261025011151.000038ef@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    [snip]
    Second, while in theory threads can be implemented by C++
    compilers+language support library, in practice I had never seen it
    done.

    This is not saying much about anything aside from the countours
    of your own experience, I'm afraid.

    (This statement remains true.)

    [snip history showing a long line of "OS Threads" implemented
    as a library]

    How any of this trivia has anything to do with real-world
    implementations of C++11 threads?

    Your statement, "while in theory threads can be implemented by
    C++ compilers+language support library, in practice I had never
    seen it done" is probably strictly true: you, individually, have
    never seen it done.

    But that does not imply that it has never been done. In
    fact, it has; many times over. There are complications, but it
    can be done. That is what I was telling you, supported by
    examples.

    The thread models adopted by both C and C++ are based on all of
    that prior art.

    I mentioned that in one of my earlier responses to boltar.
    However there exist situation in which system() is not a satisfactory >replacement for spawn(), most often because overhead of launching shell >sometimes matters.

    Let me reiterate the questions above: what do you think that a
    thread is? What do you think that a process is? And let me add
    to that, what do you think that a "shell" is?

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 13:34:58 2026
    From Newsgroup: comp.lang.c++

    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?

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 15:56:26 2026
    From Newsgroup: comp.lang.c++

    Michael S <already5chosen@yahoo.com> writes:
    On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:



    Indeed, but I'm hoping Mr Boltar will chime in with his answers,
    so that we can understand why thinks that a language like C
    should introduce a *process* model, and how threads are similar.

    - Dan C.


    First, he was talking about C++. Unlike me, he does not appear to care
    about C.
    Second, while in theory threads can be implemented by C++
    compilers+language support library, in practice I had never seen it
    done. All I had seen is C++ threads implemented in library as thin
    wrapper atop of the OS (or RT executive) implementation.
    I can not see while the same can't be done for processes, with
    API modeled on posix_spawn() or Windows CreateProcess().
    It does not look like variety in this field is bigger than in case of >threads. More like it is smaller.

    Now, would it be the first thing I would want like addition to C++
    standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...

    For which we, thankfully, have POSIX on most non-windows operating
    systems.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 15:59:52 2026
    From Newsgroup: comp.lang.c++

    cross@spitfire.i.gajendra.net (Dan Cross) writes:
    In article <20261025084234.0000449c@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    <snip>
    How any of this trivia has anything to do with real-world
    implementations of C++11 threads?

    Your statement, "while in theory threads can be implemented by
    C++ compilers+language support library, in practice I had never
    seen it done" is probably strictly true: you, individually, have
    never seen it done.

    But that does not imply that it has never been done. In
    fact, it has; many times over. There are complications, but it
    can be done. That is what I was telling you, supported by
    examples.

    Although it does, generally, rely on specific operating system
    interfaces (e.g. makecontext, setcontext, et alia).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Andreas Eder@a_eder_muc@web.de to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 16:31:56 2026
    From Newsgroup: comp.lang.c++

    On Fr 23 Okt 2026 at 22:49, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 21:00:30 -0000 (UTC), Thomas Koenig wrote:

    I have one Fortran program which has an excellent graphics API, it
    writes Postscript. Works fine. Can't do any mouse clicks on it and
    expect anything to happen, though :-)

    PostScript was a very influential graphics API, but it is only fit for
    the museum nowadays. It was designed for putting marks on paper, not
    for updating pixels on a computer screen.

    There was also display postscript from SUN.

    'Andreas
    --
    ceterum censeo redmondinem esse delendam
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 16:13:10 2026
    From Newsgroup: comp.lang.c++

    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.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 16:15:21 2026
    From Newsgroup: comp.lang.c++

    In article <YHpDS.27364$9b8f.4666@fx39.iad>,
    Scott Lurndal <slp53@pacbell.net> wrote:
    cross@spitfire.i.gajendra.net (Dan Cross) writes:
    In article <20261025084234.0000449c@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    <snip>
    How any of this trivia has anything to do with real-world
    implementations of C++11 threads?

    Your statement, "while in theory threads can be implemented by
    C++ compilers+language support library, in practice I had never
    seen it done" is probably strictly true: you, individually, have
    never seen it done.

    But that does not imply that it has never been done. In
    fact, it has; many times over. There are complications, but it
    can be done. That is what I was telling you, supported by
    examples.

    Although it does, generally, rely on specific operating system
    interfaces (e.g. makecontext, setcontext, et alia).

    That's true. But no one said that one can use strict ISO C++ to
    implement the C++ standard library.

    Regardless, if you can set the stack pointer, you can build a
    reasonable cooperative threading library purely in userspace,
    without the OS caring.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 16:17:40 2026
    From Newsgroup: comp.lang.c++

    In article <11bl9qm$10h8f$1@dont-email.me>, <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.

    In other words, you don't know.

    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.

    I'm quite sure you don't actually know.

    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?

    You've got system(), right? What, precisely, do you want this
    "multi process" API to look like?

    Take your time.

    If you want a serious answer, you've got to define your terms.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 16:29:14 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 16:15:21 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <YHpDS.27364$9b8f.4666@fx39.iad>,
    Scott Lurndal <slp53@pacbell.net> wrote:
    cross@spitfire.i.gajendra.net (Dan Cross) writes:
    In article <20261025084234.0000449c@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    <snip>
    How any of this trivia has anything to do with real-world >>>>implementations of C++11 threads?

    Your statement, "while in theory threads can be implemented by
    C++ compilers+language support library, in practice I had never
    seen it done" is probably strictly true: you, individually, have
    never seen it done.

    But that does not imply that it has never been done. In
    fact, it has; many times over. There are complications, but it
    can be done. That is what I was telling you, supported by
    examples.

    Although it does, generally, rely on specific operating system
    interfaces (e.g. makecontext, setcontext, et alia).

    That's true. But no one said that one can use strict ISO C++ to
    implement the C++ standard library.

    Regardless, if you can set the stack pointer, you can build a
    reasonable cooperative threading library purely in userspace,
    without the OS caring.

    Oh really? You seem to have forgotten about the program counter not to mentioning pushing and popping all the other cpu registers and flags at context switch.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 16:32:18 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 16:17:40 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bl9qm$10h8f$1@dont-email.me>, <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.

    In other words, you don't know.

    Oh do piss off you bore, i'm not going to humour you while you try to unpaint yourself from a corner. You clearly have no idea why C++ implements one API but not the other but you wanted to try and sound clever anyway. Whoops, didn't turn out quite how you expected did it?

    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?

    You've got system(), right? What, precisely, do you want this

    system?? ROTFL!! :)

    Oh dear, you really have no clue!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 17:14:18 2026
    From Newsgroup: comp.lang.c++

    In article <11blaui$2q6vd$1@dont-email.me>, <boltar@caprica.universe> wrote: >On Sun, 25 Oct 2026 16:17:40 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]
    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.

    In other words, you don't know.

    Oh do piss off you bore, i'm not going to humour you while
    you try to unpaint
    yourself from a corner. You clearly have no idea why C++
    implements one API
    but not the other but you wanted to try and sound clever
    anyway. Whoops, didn't
    turn out quite how you expected did it?

    Actually, it "turned out" juat about exactly as I expected it
    would.

    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?

    You've got system(), right? What, precisely, do you want this

    system?? ROTFL!! :)

    Oh dear, you really have no clue!

    You're snotty little attitude aside, I note that you can't even
    arriculate what, exactly, it is that you want. "Argument by
    insult" seems about par for the course here, but using that to
    hide your ignorance both doesn't work and makes you look
    incredbily insecure.

    Anyway, go ahead and keep flailing. Ta!

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 17:18:32 2026
    From Newsgroup: comp.lang.c++

    In article <11blaoq$2q6jk$1@dont-email.me>, <boltar@caprica.universe> wrote: >On Sun, 25 Oct 2026 16:15:21 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]
    Regardless, if you can set the stack pointer, you can build a
    reasonable cooperative threading library purely in userspace,
    without the OS caring.

    Oh really? You seem to have forgotten about the program
    counter not to
    mentioning pushing and popping all the other cpu registers
    and flags at context
    switch.

    One last hint: where do you think those thjngs arw stored? If
    you could define what a thread is, maybe you'd have a clue
    about how those are handled. :-)

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Robert Woodward@robertaw@drizzle.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 10:19:50 2026
    From Newsgroup: comp.lang.c++

    In article <11bl7vr$3nprb$2@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:

    On 10/25/26 06:34, Dan Cross wrote:
    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?

    - Dan C.

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.
    --
    "We have advanced to new and surprising levels of bafflement."
    Imperial Auditor Miles Vorkosigan describes progress in _Komarr_. rCo-----------------------------------------------------
    Robert Woodward robertaw@drizzle.com
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Cryptoengineer@petertrei@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 14:03:03 2026
    From Newsgroup: comp.lang.c++

    On 10/25/2026 1:19 PM, Robert Woodward wrote:
    In article <11bl7vr$3nprb$2@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:

    On 10/25/26 06:34, Dan Cross wrote:
    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?

    - Dan C.

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.


    Based on 40+ years of usenet experience, the only thing which will stop
    the cross posting is the death of this thread.

    pt
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Levine@johnl@taugh.com to comp.lang.c++,alt.folklore.computers on Sun Oct 25 18:17:44 2026
    From Newsgroup: comp.lang.c++

    According to <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process
    runs in its own address space. (at least these days, before virtual >>memory, who knows?)

    With copy-on-write process models the actual difference is a bit less
    clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an implementation detail. Neither process can look inside the other even if they share some unwritten or untouched pages.

    By the way, copy-on-write is quite old. See this blog post I wrote a long
    time ago:

    https://obvious.services.net/2011/01/history-of-copy-on-write-memory.html
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 12:21:01 2026
    From Newsgroup: comp.lang.c++

    Cryptoengineer wrote:
    On 10/25/2026 1:19 PM, Robert Woodward wrote:
    In article <11bl7vr$3nprb$2@dont-email.me>,
    -a Peter Flass <Peter@Iron-Spring.com> wrote:

    On 10/25/26 06:34, Dan Cross wrote:
    In article <11bkfcc$104cc$1@dont-email.me>,-a <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?

    -a-a-a-a- Dan C.

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.


    Based on 40+ years of usenet experience, the only thing which will stop
    the cross posting is the death of this thread.

    pt

    What struck me about Game of Thrones was that the monarchy existed in
    Game of Thrones for the sole reason of some guys conspiring in Chapter
    One about taking it for themselves. What a bunch of polymaths.
    --
    Can you strip away so we may start again?
    "ThererCOs a switch and they don't
    seem authentic or themselves. It
    feels like IrCOm an unnecessary
    body and itrCOs a waste of time to
    even be there." -- Grim, playful Blaine.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brown@david.brown@hesbynett.no to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:26:41 2026
    From Newsgroup: comp.lang.c++

    On 25/10/2026 18:19, Robert Woodward wrote:
    In article <11bl7vr$3nprb$2@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:

    On 10/25/26 06:34, Dan Cross wrote:
    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?

    - Dan C.

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.


    Was it ever relevant to that group? At least one person in this thread
    is renowned for his irritating habit of adding every newsgroup he can
    think of to lists. "This post is in English - I'll add
    alt.languages.english to the list. I see there was a number mentioned -
    I've added sci.maths for their thoughts. I've just thought about
    thoughts, so alt.philosophy is needed too". Anyone who feels that might
    refer to them could do their part towards making the world a nicer
    place, and either quit that habit, or leave Usenet.

    As I don't follow any of these groups other than C++, I can't say if it
    is topical or not in the other groups. I certainly don't mind if
    irrelevant groups are removed, but there is a real risk that some twit
    will re-add them. Then you still have the pointless (to you) threads,
    but now they are also fragmented.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 12:29:18 2026
    From Newsgroup: comp.lang.c++

    David Brown wrote:
    On 25/10/2026 18:19, Robert Woodward wrote:
    In article <11bl7vr$3nprb$2@dont-email.me>,
    -a Peter Flass <Peter@Iron-Spring.com> wrote:

    On 10/25/26 06:34, Dan Cross wrote:
    In article <11bkfcc$104cc$1@dont-email.me>,-a <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?

    -a-a-a-a- Dan C.

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.


    Was it ever relevant to that group?-a At least one person in this thread
    is renowned for his irritating habit of adding every newsgroup he can
    think of to lists.-a "This post is in English - I'll add alt.languages.english to the list.-a I see there was a number mentioned - I've added sci.maths for their thoughts.-a I've just thought about
    thoughts, so alt.philosophy is needed too".

    Sorry about that. I only did it because Eternal September, if I take
    away one of the Newsgroups: listings, it won't let me post. In such a
    case it only allows 3 newsgroups. That won't do for this thread.
    --
    Can you strip away so we may start again?
    "ThererCOs a switch and they don't
    seem authentic or themselves. It
    feels like IrCOm an unnecessary
    body and itrCOs a waste of time to
    even be there." -- Grim, playful Blaine.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brown@david.brown@hesbynett.no to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:59:50 2026
    From Newsgroup: comp.lang.c++

    On 25/10/2026 19:29, Blaine wrote:
    David Brown wrote:
    On 25/10/2026 18:19, Robert Woodward wrote:
    In article <11bl7vr$3nprb$2@dont-email.me>,
    -a Peter Flass <Peter@Iron-Spring.com> wrote:

    On 10/25/26 06:34, Dan Cross wrote:
    In article <11bkfcc$104cc$1@dont-email.me>,-a <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?

    -a-a-a-a- Dan C.

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.


    Was it ever relevant to that group?-a At least one person in this
    thread is renowned for his irritating habit of adding every newsgroup
    he can think of to lists.-a "This post is in English - I'll add
    alt.languages.english to the list.-a I see there was a number mentioned
    - I've added sci.maths for their thoughts.-a I've just thought about
    thoughts, so alt.philosophy is needed too".

    Sorry about that. I only did it because Eternal September, if I take
    away one of the Newsgroups: listings, it won't let me post. In such a
    case it only allows 3 newsgroups. That won't do for this thread.


    I was not thinking of you. (And in the case of this thread, the
    original poster cross-posted wildly to start with.)

    I've nothing against the occasional cross-post thread, and some threads
    can be relevant to multiple groups. A comparison to C++ and Fortran
    could easily be relevant to c.l.fortran and c.l.c++. It's mass
    cross-posting to irrelevant groups that bugs me (and many others).

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 20:07:20 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 16:31:56 +0100, Andreas Eder wrote:

    On Fr 23 Okt 2026 at 22:49, Lawrence DrCOOliveiro wrote:

    PostScript was a very influential graphics API, but it is only fit
    for the museum nowadays. It was designed for putting marks on
    paper, not for updating pixels on a computer screen.

    There was also display postscript from SUN.

    Display PostScript was from Adobe.

    You could be thinking of NeWS, which was from Sun. It slightly
    predated X11, and they pretty much abandoned it after adopting X11
    wholesale, like the entire rest of the Unix industry.

    But neither Display PostScript nor NeWS made any changes to the
    PostScript graphics model; it was still designed around making marks
    on paper, not for updating pixels on a computer screen.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 22:24:14 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 08:37:22 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sat, 24 Oct 2026 21:24:58 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bj08r$309uk$1@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/24/26 09:41, Dan Cross wrote:
    In article <11bhppd$2lpkc$1@dont-email.me>,
    <boltar@caprica.universe>
    wrote:
    On Fri, 23 Oct 2026 20:45:27 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bf4d1$skul$1@dont-email.me>,
    <boltar@caprica.universe>
    wrote:
    On Thu, 22 Oct 2026 16:22:30 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bd7rg$2cvfs$1@dont-email.me>,
    <boltar@battlestar.co.uk>
    wrote:

    You need an OS to do threading properly too. Theres a reason >>>>>>>> green
    threads
    in java were a joke.

    Weird that you think you need a operating system for threads,
    yet you want C to standardize processes which also ... need an >>>>>>> operating system. I mean, POSIX already does an ok job of
    standardizing the sorts of process-y things you would expect
    from, you know, an operating system.

    I'm simply pointing out the inconsistency in having a
    threading library
    but
    not a process library. Its perfectly possible to simulate a
    multiprocess enviroment.

    So write a simulator in your language of choice. You don't need
    the language to standardize a process model for that.

    Ditto threads. So why does C++ have a threading library?

    Take your time...

    What, pray tell, do you think that a _thread_ is? And how is it
    different from a _process_? For that matter, what do you think
    that a _process_ is?

    Please, take all the time you need to answer.

    Threads share resources such as address space, files, etc. A
    process runs in its own address space. (at least these days, before >>virtual memory, who knows?)

    Indeed, but I'm hoping Mr Boltar will chime in with his answers,
    so that we can understand why thinks that a language like C
    should introduce a *process* model, and how threads are similar.

    Who mentioned C? I was talking about C++ which has a threading API
    already. Do try and keep up.


    In that regard, C and C++ are very similar.
    Similar primitives modeled mostly on Posix threads were added to both
    languages at approximately the same time.
    https://en.cppreference.com/c/thread

    The difference is not in this specific case, but in generally more
    conservative attitude of C committee relatively to its C++ counterpart
    w.r.t. extending Standard library.






    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Titus G@noone@nowhere.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 09:43:31 2026
    From Newsgroup: comp.lang.c++

    On 26/10/2026 06:19, Robert Woodward wrote:
    In article <11bl7vr$3nprb$2@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:

    snip

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.

    Yes. You are correct, but there are several from r.a.sf.written making a contribution and although it is mainly above my pay grade, I am still
    reading. In Thunderbird, it is extremely easy to mark a thread as
    ignored after which you will not be annoyed by further posts on that
    topic. Easier than complaining.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 22:56:19 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 08:41:48 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <20261025011151.000038ef@yahoo.com>,
    Now, would it be the first thing I would want like addition to C++ >>standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...

    POSIX has all of that. POSIX also has a process model. Why not
    just make POSIX a part of the language, then? (Answer that and
    you may start to understand why this is harder than it looks
    for C++ [and C].)

    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.

    Actually, implementing C++11 (or C11) threads fully in user space on
    pre-Vista Win32 (i.e. before addition of support for conditional
    variables to OS API) would be quite challenging. I don't know if
    anybody bothered.
    I think that it is possible, but if you want it robust then it (cond. variables) will cost you significant overhead relatively to "native" synchronization primitives.

    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.


    Dick-measuring competitions are integral part of Usenet tradition.






    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Moylan@peter@pmoylan.org to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 08:29:03 2026
    From Newsgroup: comp.lang.c++

    On 24/10/26 06:49, Lynn McGuire wrote:

    Bill Gates wrote the Microsoft Basic compiler and interpreter for the
    Altair 8080 in 2K of ram using assembly language. Take that as you will.

    Then someone translated it into an African language and called it Mbasic.
    --
    Peter Moylan peter@pmoylan.org http://www.pmoylan.org
    Newcastle, NSW
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 14:36:44 2026
    From Newsgroup: comp.lang.c++

    On 10/25/2026 1:07 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 16:31:56 +0100, Andreas Eder wrote:

    On Fr 23 Okt 2026 at 22:49, Lawrence DrCOOliveiro wrote:

    PostScript was a very influential graphics API, but it is only fit
    for the museum nowadays. It was designed for putting marks on
    paper, not for updating pixels on a computer screen.

    There was also display postscript from SUN.

    Display PostScript was from Adobe.

    You could be thinking of NeWS, which was from Sun. It slightly
    predated X11, and they pretty much abandoned it after adopting X11
    wholesale, like the entire rest of the Unix industry.

    But neither Display PostScript nor NeWS made any changes to the
    PostScript graphics model; it was still designed around making marks
    on paper, not for updating pixels on a computer screen.

    Updating pixels on a computer screen? Use a frag shader.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Nuno Silva@nunojsilva@invalid.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.folklore.computers on Sun Oct 25 23:48:24 2026
    From Newsgroup: comp.lang.c++

    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
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:54:40 2026
    From Newsgroup: comp.lang.c++

    On 10/25/26 13:43, Titus G wrote:
    On 26/10/2026 06:19, Robert Woodward wrote:
    In article <11bl7vr$3nprb$2@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:

    snip

    I vote that alt.folklore.computers gets pruned from the list of
    recipients, as this discussion seems irrelevant here.

    For that matter, this entire thread has ceased to have anything to do
    with rec.arts.sf.written.

    Yes. You are correct, but there are several from r.a.sf.written making a contribution and although it is mainly above my pay grade, I am still reading. In Thunderbird, it is extremely easy to mark a thread as
    ignored after which you will not be annoyed by further posts on that
    topic. Easier than complaining.

    But a lot less fun!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 09:51:51 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 17:14:18 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11blaui$2q6vd$1@dont-email.me>, <boltar@caprica.universe> wrote: >>anyway. Whoops, didn't
    turn out quite how you expected did it?

    Actually, it "turned out" juat about exactly as I expected it
    would.

    You have low expectations then.

    Oh dear, you really have no clue!

    You're snotty little attitude aside, I note that you can't even

    Anyone who equates system() with multiprocess programming doesn't know wtf they're talking about. Hows that for a snotty aside?

    arriculate what, exactly, it is that you want. "Argument by
    insult" seems about par for the course here, but using that to
    hide your ignorance both doesn't work and makes you look
    incredbily insecure.

    Anyway, go ahead and keep flailing. Ta!

    Go ahead and remain clueless.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 09:54:22 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 17:18:32 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11blaoq$2q6jk$1@dont-email.me>, <boltar@caprica.universe> wrote: >>On Sun, 25 Oct 2026 16:15:21 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]
    Regardless, if you can set the stack pointer, you can build a
    reasonable cooperative threading library purely in userspace,
    without the OS caring.

    Oh really? You seem to have forgotten about the program
    counter not to
    mentioning pushing and popping all the other cpu registers
    and flags at context
    switch.

    One last hint: where do you think those thjngs arw stored? If
    you could define what a thread is, maybe you'd have a clue
    about how those are handled. :-)

    Oh please, try a bit harder. You can do anything you want in ring 0 assembler, that doesn't mean its a good idea.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.c++,alt.folklore.computers on Mon Oct 26 09:57:37 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process >>>runs in its own address space. (at least these days, before virtual >>>memory, who knows?)

    With copy-on-write process models the actual difference is a bit less
    clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an implementation >detail. Neither process can look inside the other even if they share some >unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation processes don't share any virtual memory at all - everything is copied to a new location at fork - so you can't use sharing memory as a way to demarcate multithreading and multiprocess.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 09:59:11 2026
    From Newsgroup: comp.lang.c++

    On Sun, 25 Oct 2026 22:56:19 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sun, 25 Oct 2026 08:41:48 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <20261025011151.000038ef@yahoo.com>,
    Now, would it be the first thing I would want like addition to C++
    standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...

    POSIX has all of that. POSIX also has a process model. Why not
    just make POSIX a part of the language, then? (Answer that and
    you may start to understand why this is harder than it looks
    for C++ [and C].)

    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.

    Actually, implementing C++11 (or C11) threads fully in user space on >pre-Vista Win32 (i.e. before addition of support for conditional
    variables to OS API) would be quite challenging. I don't know if
    anybody bothered.
    I think that it is possible, but if you want it robust then it (cond. >variables) will cost you significant overhead relatively to "native" >synchronization primitives.

    C++ threading didn't have 3 level locking until 2017 making it effectively useless IMO. Perhaps that was down to the lowest common denominator called Windows.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.c++,alt.folklore.computers on Mon Oct 26 03:53:45 2026
    From Newsgroup: comp.lang.c++

    On 10/26/26 02:57, boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process
    runs in its own address space. (at least these days, before virtual
    memory, who knows?)

    With copy-on-write process models the actual difference is a bit less
    clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an implementation >> detail. Neither process can look inside the other even if they share some >> unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation processes don't share any virtual memory at all - everything is copied to a new location
    at fork - so you can't use sharing memory as a way to demarcate multithreading
    and multiprocess.

    In the old days before IUCV or VMCF I did a multi-process application on
    VM by using a file to pass data among processes. Surprisingly, it worked
    well.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From kludge@kludge@panix.com (Scott Dorsey) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 09:50:47 2026
    From Newsgroup: comp.lang.c++

    In article <11bn80e$11hkj$1@dont-email.me>, <boltar@caprica.universe> wrote: >Oh please, try a bit harder. You can do anything you want in ring 0 assembler,
    that doesn't mean its a good idea.

    As someone who is spending his morning writing 8051 code, I think it can be
    a very very good idea.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 14:41:54 2026
    From Newsgroup: comp.lang.c++

    boltar@caprica.universe writes:
    On Sun, 25 Oct 2026 22:56:19 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sun, 25 Oct 2026 08:41:48 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <20261025011151.000038ef@yahoo.com>,
    Now, would it be the first thing I would want like addition to C++
    standard library? No it would not be.
    The first thing would be IPv4 communication, sockets, poll etc...

    POSIX has all of that. POSIX also has a process model. Why not
    just make POSIX a part of the language, then? (Answer that and
    you may start to understand why this is harder than it looks
    for C++ [and C].)

    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.

    Actually, implementing C++11 (or C11) threads fully in user space on >>pre-Vista Win32 (i.e. before addition of support for conditional
    variables to OS API) would be quite challenging. I don't know if
    anybody bothered.
    I think that it is possible, but if you want it robust then it (cond. >>variables) will cost you significant overhead relatively to "native" >>synchronization primitives.

    C++ threading didn't have 3 level locking until 2017 making it effectively >useless IMO. Perhaps that was down to the lowest common denominator called >Windows.


    Mind defining your terminology? "3 level locking", in particular?

    Assigning a canonical "lock number" to each lock, and failing a lock
    request for a lock with a lower number than that already held is
    a design pattern that has been around since 1980 (in Burroughs
    mainframes it was implemented in hardware). Easy enough to do
    prior to C++17 in software.

    And your assertion that a language that doesn't support it intrinsically
    is "useless" is ridiculous.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.lang.c++,alt.folklore.computers on Mon Oct 26 14:44:59 2026
    From Newsgroup: comp.lang.c++

    Peter Flass <Peter@Iron-Spring.com> writes:
    On 10/26/26 02:57, boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process >>>>> runs in its own address space. (at least these days, before virtual
    memory, who knows?)

    With copy-on-write process models the actual difference is a bit less
    clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an implementation >>> detail. Neither process can look inside the other even if they share some >>> unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation processes
    don't share any virtual memory at all - everything is copied to a new location
    at fork - so you can't use sharing memory as a way to demarcate multithreading
    and multiprocess.

    In the old days before IUCV or VMCF I did a multi-process application on
    VM by using a file to pass data among processes. Surprisingly, it worked >well.

    Burroughs had both a synchronous 'core2core' interface between processes
    as well as asynchronous storage queues. In the days of small address spaces, those were invaluable interfaces.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.c++,alt.folklore.computers on Mon Oct 26 08:56:19 2026
    From Newsgroup: comp.lang.c++

    On 10/26/26 07:44, Scott Lurndal wrote:
    Peter Flass <Peter@Iron-Spring.com> writes:
    On 10/26/26 02:57, boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process >>>>>> runs in its own address space. (at least these days, before virtual >>>>>> memory, who knows?)

    With copy-on-write process models the actual difference is a bit less >>>>> clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an implementation
    detail. Neither process can look inside the other even if they share some >>>> unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation processes
    don't share any virtual memory at all - everything is copied to a new location
    at fork - so you can't use sharing memory as a way to demarcate multithreading
    and multiprocess.

    In the old days before IUCV or VMCF I did a multi-process application on
    VM by using a file to pass data among processes. Surprisingly, it worked
    well.

    Burroughs had both a synchronous 'core2core' interface between processes
    as well as asynchronous storage queues. In the days of small address spaces, those were invaluable interfaces.

    It took IBM a little longer for this, but eventually they got there.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.c++,alt.folklore.computers on Mon Oct 26 16:19:35 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 03:53:45 -0700
    Peter Flass <Peter@Iron-Spring.com> gabbled:
    On 10/26/26 02:57, boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process >>>>> runs in its own address space. (at least these days, before virtual
    memory, who knows?)

    With copy-on-write process models the actual difference is a bit less
    clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an implementation >>> detail. Neither process can look inside the other even if they share some >>> unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation processes

    don't share any virtual memory at all - everything is copied to a new >location
    at fork - so you can't use sharing memory as a way to demarcate >multithreading
    and multiprocess.

    In the old days before IUCV or VMCF I did a multi-process application on
    VM by using a file to pass data among processes. Surprisingly, it worked >well.

    I'd be interested how you'd implement fork() using that method given you
    need to copy the state of all file descriptors, heap, stack and global
    memory, current working directory, enviroment variables and a ton of other things I can't remember without googling.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 16:16:46 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 14:41:54 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:
    boltar@caprica.universe writes:
    C++ threading didn't have 3 level locking until 2017 making it effectively >>useless IMO. Perhaps that was down to the lowest common denominator called >>Windows.


    Mind defining your terminology? "3 level locking", in particular?

    If you have to ask....

    1. No lock
    2. Write lock - Read only access, writer blocked until all readers out of critic
    al section)
    3. Read-write lock - all threads other than the one in section block)

    This is basic stuff FFS. C++ finally got around to #2 with shared_mutex in
    2017 and its rather critical for certain algorithms.

    Assigning a canonical "lock number" to each lock, and failing a lock
    request for a lock with a lower number than that already held is
    a design pattern that has been around since 1980 (in Burroughs
    mainframes it was implemented in hardware). Easy enough to do
    prior to C++17 in software.

    Thats something else entirely.

    And your assertion that a language that doesn't support it intrinsically
    is "useless" is ridiculous.

    Not useless then, just less useful.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 16:58:01 2026
    From Newsgroup: comp.lang.c++

    In article <11bnlrn$ghl$1@panix2.panix.com>,
    Scott Dorsey <kludge@panix.com> wrote:
    In article <11bn80e$11hkj$1@dont-email.me>, <boltar@caprica.universe> wrote: >>Oh please, try a bit harder. You can do anything you want in ring 0 assembler,
    that doesn't mean its a good idea.

    As someone who is spending his morning writing 8051 code, I think it can be
    a very very good idea.

    The irony is that, by definition, if you are running something
    in userspace, it's not in "Ring 0" anyway.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.c++,alt.folklore.computers on Mon Oct 26 11:46:38 2026
    From Newsgroup: comp.lang.c++

    On 10/26/26 09:19, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 03:53:45 -0700
    Peter Flass <Peter@Iron-Spring.com> gabbled:
    On 10/26/26 02:57, boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to-a <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process >>>>>> runs in its own address space. (at least these days, before virtual >>>>>> memory, who knows?)

    With copy-on-write process models the actual difference is a bit less >>>>> clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an
    implementation
    detail.-a Neither process can look inside the other even if they
    share some
    unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation
    processes

    don't share any virtual memory at all - everything is copied to a new
    location
    at fork - so you can't use sharing memory as a way to demarcate
    multithreading
    and multiprocess.

    In the old days before IUCV or VMCF I did a multi-process application
    on VM by using a file to pass data among processes. Surprisingly, it
    worked well.

    I'd be interested how you'd implement fork() using that method given you
    need to copy the state of all file descriptors, heap, stack and global memory, current working directory, enviroment variables and a ton of other things I can't remember without googling.

    No fork. Each VM had a single thread of execution. I was happy to get
    multiple processes to cooperate. It was a master process (virtual
    machine) that distributed work to worker machines.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:10:46 2026
    From Newsgroup: comp.lang.c++

    boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 14:22:34 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
    The differences are utterly irrelevant when it comes to prividing a
    common
    API to the functionality but thank you for demonstrating you had no
    answer
    to my question.


    Ummm... It is relevant. Every process has a single thread of
    execution, but not all processes have multiple threads.

    No shit sherlock, thanks for the heads up. Your point is?

    Basically that methinks you insult too much. Your wisdom here isn't
    worth a sack of beans. I haven't learned one thing from you.
    --
    Can you strip away so we may start again?
    "ThererCOs a switch and they don't
    seem authentic or themselves. It
    feels like IrCOm an unnecessary
    body and itrCOs a waste of time to
    even be there." -- Grim, playful Blaine.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From kludge@kludge@panix.com (Scott Dorsey) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 15:32:52 2026
    From Newsgroup: comp.lang.c++

    Dan Cross <cross@spitfire.i.gajendra.net> wrote:
    In article <11bnlrn$ghl$1@panix2.panix.com>,
    Scott Dorsey <kludge@panix.com> wrote:
    In article <11bn80e$11hkj$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>Oh please, try a bit harder. You can do anything you want in ring 0 assembler,
    that doesn't mean its a good idea.

    As someone who is spending his morning writing 8051 code, I think it can be >>a very very good idea.

    The irony is that, by definition, if you are running something
    in userspace, it's not in "Ring 0" anyway.

    On the 8051 there is only one ring. It is like Middle Earth in that regard.
    It does have an atomic test and set instruction, though, which is more than
    I can say for some machines.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 21:45:17 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 14:41:54 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:
    boltar@caprica.universe writes:
    C++ threading didn't have 3 level locking until 2017 making it >>effectively useless IMO. Perhaps that was down to the lowest common >>denominator called Windows.


    Mind defining your terminology? "3 level locking", in particular?

    If you have to ask....

    1. No lock
    2. Write lock - Read only access, writer blocked until all readers
    out of critic al section)
    3. Read-write lock - all threads other than the one in section block)


    Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
    time as conditional variables. 5 years before C++11. https://learn.microsoft.com/en-us/windows/win32/sync/slim-reader-writer--srw--locks
    Of course WinXP remained popular for few more years, approximately up
    until 2nd half of 2010, but that too predates publication of C++11 in
    2011-09.

    This is basic stuff FFS. C++ finally got around to #2 with
    shared_mutex in 2017 and its rather critical for certain algorithms.

    Assigning a canonical "lock number" to each lock, and failing a lock >request for a lock with a lower number than that already held is
    a design pattern that has been around since 1980 (in Burroughs
    mainframes it was implemented in hardware). Easy enough to do
    prior to C++17 in software.

    Thats something else entirely.

    And your assertion that a language that doesn't support it
    intrinsically is "useless" is ridiculous.

    Not useless then, just less useful.


    I never ever used what you call "3 level locking", not even by mistake.
    But then, I don't write complicated apps on "big" computers day in day
    out.






    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 22:04:33 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 25 Oct 2026 17:14:18 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11blaui$2q6vd$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    anyway. Whoops, didn't
    turn out quite how you expected did it?

    Actually, it "turned out" juat about exactly as I expected it
    would.

    You have low expectations then.

    Oh dear, you really have no clue!

    You're snotty little attitude aside, I note that you can't even

    Anyone who equates system() with multiprocess programming doesn't
    know wtf they're talking about. Hows that for a snotty aside?

    arriculate what, exactly, it is that you want. "Argument by
    insult" seems about par for the course here, but using that to
    hide your ignorance both doesn't work and makes you look
    incredbily insecure.

    Anyway, go ahead and keep flailing. Ta!

    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.
    The problem with system() is not that. Often not even an efficiency.
    The problem with system() identified most easily if we ask ourself "Why
    do we want xyz in standard library?"
    Sometimes the answer is "because functionality is not available
    otherwise".
    But more often functonality is available in native OS API. Not just
    that, typically functionality of native APIs is better than one of
    standard language library.
    So, what is the other reason? It is portability at source level + "learn
    once use everywhere".
    Here system() fails. That is, the function is the same everywhere, but
    string argument is OS-dependent. So, system() may be achieves
    functionality, but does not really help portability.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 22:09:01 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 25 Oct 2026 14:19:14 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/25/2026 1:34 AM, boltar@caprica.universe wrote:
    On Sat, 24 Oct 2026 13:57:02 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    In article <11bif5s$2pam0$1@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:
    You can have co-operative threads. IBM CICS used to run lots of
    threads (tasks) concurrently, and ran them well.

    When I learned C, there was no threading and there were only
    different processes, so you had to do a fork and then synchronize
    with the other process. This wasn't a dealbreaker and we did
    plenty of stuff that way, but having threads available was very
    nice and made for many operations becoming more convenient to
    write.

    Unfortunately most win32 programmers don't really understand
    multiprocess programming because the w32 API is so borked so use
    threads even when seperate process would be more appropriate.



    Windows has what we need to run multi process. Even for a Mutex... >Remember WAIT_ABANDONED?

    win32 can't do fork() making it effectively a totally useless API for
    a lot of multiprocess development. Creating a brand new process is
    fine if you don't need any complicated shared state such as when
    kicking off something on the command line or creating a pipe
    (something else win32 is shit at) but thats about it.


    You are clueless about Windows. That's o.k.
    Your pretense that you know something about it is not o.k.
    In that regard you are not better than LDO.






    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.c++,alt.folklore.computers on Mon Oct 26 13:19:14 2026
    From Newsgroup: comp.lang.c++

    On 10/26/2026 9:19 AM, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 03:53:45 -0700
    Peter Flass <Peter@Iron-Spring.com> gabbled:
    On 10/26/26 02:57, boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to-a <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process >>>>>> runs in its own address space. (at least these days, before virtual >>>>>> memory, who knows?)

    With copy-on-write process models the actual difference is a bit less >>>>> clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an
    implementation
    detail.-a Neither process can look inside the other even if they
    share some
    unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation
    processes

    don't share any virtual memory at all - everything is copied to a new
    location
    at fork - so you can't use sharing memory as a way to demarcate
    multithreading
    and multiprocess.

    In the old days before IUCV or VMCF I did a multi-process application
    on VM by using a file to pass data among processes. Surprisingly, it
    worked well.

    I'd be interested how you'd implement fork() using that method given you
    need to copy the state of all file descriptors, heap, stack and global memory, current working directory, enviroment variables and a ton of other things I can't remember without googling.


    Why even do that? Sigh.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.c++,alt.folklore.computers on Mon Oct 26 13:19:49 2026
    From Newsgroup: comp.lang.c++

    On 10/26/2026 11:46 AM, Peter Flass wrote:
    On 10/26/26 09:19, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 03:53:45 -0700
    Peter Flass <Peter@Iron-Spring.com> gabbled:
    On 10/26/26 02:57, boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 18:17:44 -0000 (UTC)
    John Levine <johnl@taugh.com> gabbled:
    According to-a <boltar@caprica.universe>:
    Threads share resources such as address space, files, etc. A process >>>>>>> runs in its own address space. (at least these days, before virtual >>>>>>> memory, who knows?)

    With copy-on-write process models the actual difference is a bit less >>>>>> clear cut.

    Copy-on-write (or on some older systems copy-on-touch) is an
    implementation
    detail.-a Neither process can look inside the other even if they
    share some
    unwritten or untouched pages.

    The point is they are sharing memory. In a reference implementation
    processes

    don't share any virtual memory at all - everything is copied to a new
    location
    at fork - so you can't use sharing memory as a way to demarcate
    multithreading
    and multiprocess.

    In the old days before IUCV or VMCF I did a multi-process application
    on VM by using a file to pass data among processes. Surprisingly, it
    worked well.

    I'd be interested how you'd implement fork() using that method given you
    need to copy the state of all file descriptors, heap, stack and global
    memory, current working directory, enviroment variables and a ton of
    other
    things I can't remember without googling.

    No fork. Each VM had a single thread of execution. I was happy to get multiple processes to cooperate. It was a master process (virtual
    machine) that distributed work to worker machines.

    That works well.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 22:40:55 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 13:12:24 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote:

    On 10/26/2026 12:45 PM, Michael S wrote:
    On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 14:41:54 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:
    boltar@caprica.universe writes:
    C++ threading didn't have 3 level locking until 2017 making it
    effectively useless IMO. Perhaps that was down to the lowest
    common denominator called Windows.


    Mind defining your terminology? "3 level locking", in
    particular?

    If you have to ask....

    1. No lock
    2. Write lock - Read only access, writer blocked until all readers
    out of critic al section)
    3. Read-write lock - all threads other than the one in section
    block)

    Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
    time as conditional variables. 5 years before C++11. https://learn.microsoft.com/en-us/windows/win32/sync/slim-reader-writer--srw--locks
    Of course WinXP remained popular for few more years, approximately
    up until 2nd half of 2010, but that too predates publication of
    C++11 in 2011-09.

    This is basic stuff FFS. C++ finally got around to #2 with
    shared_mutex in 2017 and its rather critical for certain
    algorithms.
    Assigning a canonical "lock number" to each lock, and failing a
    lock request for a lock with a lower number than that already
    held is a design pattern that has been around since 1980 (in
    Burroughs mainframes it was implemented in hardware). Easy
    enough to do prior to C++17 in software.

    Thats something else entirely.

    And your assertion that a language that doesn't support it
    intrinsically is "useless" is ridiculous.

    Not useless then, just less useful.


    I never ever used what you call "3 level locking", not even by
    mistake. But then, I don't write complicated apps on "big"
    computers day in day out.
    Still don't really know what he means by 3 level locking. Using lock
    hashing where an address is hashed into a lock index such that no
    object needs its own lock is nothing new. But it needs to be sorted
    and deduped.


    He explained it in the post above.
    It seem that he mistyped few things in explanation, but it is possible
    to understand intentions. He is talking about std::shared_mutex.






    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 21:59:06 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 13:03:25 -0700, Chris M. Thomasson wrote:

    Shared state? Just use memory mapped files. You don't need
    pipes/sockets etc. You need to know how to properly sync things.

    Like it or not, the Unix-type model is the closest we have to a
    standard set of OS APIs. ItrCOs the only one that starts from an
    official spec, namely POSIX.

    At one point, Sun did spearhead a campaign to standardize Microsoft
    Windows, believe it or not
    <https://www.youtube.com/watch?v=H5v0CK249rI> -- but of course
    Microsoft successfully stymied that effort.

    And as a result of all that past market strategizing, nowadays we have
    a multi-decade-long accumulation of Free software that assumes that
    basic Unix-type set of APIs, and nothing else is able to come close.
    So that is what we expect to have when we start new projects or keep
    existing ones going, because nobody wants to reinvent the wheel when
    they can build on all the high-quality work that has gone before.

    Like it or not, the Unix model has conquered the world.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn Wheeler@lynn@garlic.com to comp.lang.c++,alt.folklore.computers on Mon Oct 26 13:36:29 2026
    From Newsgroup: comp.lang.c++

    Peter Flass <Peter@Iron-Spring.com> writes:
    In the old days before IUCV or VMCF I did a multi-process application
    on VM by using a file to pass data among processes. Surprisingly, it
    worked well.

    Some of the MIT CTSS/7094 people went to the 5th flr for Multics (which
    spawns unix). Others went to the 4th flr for IBM Cambridge Scientific
    Center and did virtual machines (originally wanted 360/50 to hardware
    mods adding virtual memory, but all the spare ones were going to FAA ATC effort, so they had to settle for 360/40 and did CP40/CMS, which morphs
    into CP67/CMS when 360/67 standard with virtual memory becomes
    available), science center wide-area network which mophs into the
    internal corporate network RSCS/VNET (larger than arpanet/internet from
    the beginning until sometime mid/late 80s about the time it was force to convert to SNA/VTAM), performance and online apps (including email, ctss
    runoff became "script", invented GML in 1969 and GML tags added to
    script), etc.

    SPM was done by IBM Pisa Scientific Center for CP/67. In the decision to
    add virtual memory to all 370s, some of the CSC people went to 3rd flr
    taking over the IBM Boston Programming Center for the vm370 development
    group, in the morph of CP67->VM370 lots of stuff was simplified and/or
    dropped. When I joined IBM, one of my hobbies was enhanced production
    operating systems for internal datacenters. For VM370R2-base, I started
    adding lots of stuff back in for my CSC/VM (and it included SPM)

    Then for VM370R3-base CSC/VM, I added lot more stuff back in, including multiprocessor support. The development group had introduced VMCF in
    VM370R3. Then the head of POK (high-end 370s) had convinced corporate to
    kill VM370, shutdown the development group and transfer all the people
    to POK for MVS/XA. Endicott (mid-range 370s) was able to acquire the
    VM370 product mission but had to recreate a development group from
    scratch. For VM370, Endicott introduces IUCV and SMSG.

    However, one of the issues was that SPM (from CP67) was a superset of
    VMCF, IUCV, and SMSG.

    trivia: The REXX author did a multi-user, client/server, SPM-based
    spacewar game and since RSCS/VNET had full SPM support, clients weren't
    limited to the same physical machine as the server (anywhere on internal network). note: almost immediately robot clients appeared beating all
    human clients. the server then was tweaked to increase power use
    non-linear as client responses dropped below human threasholds.
    --
    virtualization experience starting Jan1968, online at home since Mar1970
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to comp.lang.fortran,comp.lang.c++,alt.folklore.computers on Mon Oct 26 19:14:57 2026
    From Newsgroup: comp.lang.c++

    On 10/22/2026 07:50, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 19:01:38 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:
    In article <11bb1da$qfn9$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>> Not sure why you think its conspiracy anything. I use the language on a
    daily basis and everytime a new version comes out I hope they've added
    something useful but since 2014 its been a law of diminishing returns.
    Plus there's unexplained omissions - eg threads have been part of the core >>> language since 2011. Great, but what about processes? When do we get them? >>> Sure, I could just use fork() but then I could also just use pthread_create()
    too.

    One can implement a pretty reasonable threads library given the
    virtual machine model of standard C or C++. Processes? With

    Virtual machine? Wrong language , comp.lang.java is that way --->

    their own address spaces, credentials, resource limits, IPC
    mechanisms, potentially running different programs, and so on?

    Not so much. You need an operating system for that, son.

    You need an OS to do threading properly too. Theres a reason green threads
    in java were a joke.
    Processes are almost self-contained virtual machines. Unix has one of
    the cleanest implementations around, and the fork() system call combined
    with copy-on-write is very elegant. None of the other operating system I
    have worked with have anything remotely like it. VMS was also quite
    elegant, but so different that I think it would be impossible to
    simulate one on the other (in either direction).

    Threads are much simpler. Multiple strands of execution in a shared
    address space. All the language needs to do is provide one shared
    vocabulary to allow code portability.

    To me it is obvious that threads can and should be standardized, while processes are generally not portable.

    But if you hotheads can't agree on that, can you please now agree to
    disagree and shut up!
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 19:43:04 2026
    From Newsgroup: comp.lang.c++

    On 10/24/2026 2:38 PM, Charlie Gibbs wrote:
    On 2026-10-24, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 10/23/2026 8:44 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 23:31:41 GMT, Charlie Gibbs wrote:

    On 2026-10-23, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    What was that error message? I was expecting something like rCLDISK
    ERRORrCY or rCLI/O ERRORrCY. Instead, it said

    IrCOm having trouble with the disk.

    The idea of an error message phrased in plain, approachable
    language (using a first-person pronoun, even) instead of technical
    terms?? That was a revelation.

    Unfortunately it's not the kind of revelation I welcome. Back in my
    mainframe days, I learned to hate catch-all error messages; they're
    the sign of a programmer who's too lazy to try to help the user. If
    something goes wrong, I want to be given some clues as to where to
    look. But more and more these days, your typical error message is
    "Something went wrong." Nothing more. This kind of conduct should be
    condemned.

    This was not like that though, was it? On systems of that era, you
    would typically get something like rCLDISK ERRORrCY or rCLI/O ERRORrCY. The >>> plain-language message was no less specific than that.

    Do you want more detail about what went wrong? Perhaps a CRC
    validation failure? Sector-addressing failure? Missing address/data
    marks? Invalid GCR/RLL encoding?

    That kind of low-level detail might be helpful to somebody (perhaps a
    hardware engineer) trying to fix the problem. And perhaps it should
    appear in a system log somewhere.

    And it wouldnrCOt have mattered much in this case, anyway, since it
    would have been obvious to anybodyrCi sitting or standing in front of the >>> machine, that the most likely cause was the fact that there was no
    disk in the drive.

    rCiAnybody who had made much use of floppy disks on micros, anyway.

    Iirc, BASIC had a fun error. I cannot remember the damn exact phrase, it
    was something like expression too complex or something.

    "Who is General Failure and why is he reading my disk?"


    :^() Basically. The BASIC was about too complex, and it was a little odd
    to me.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 19:51:23 2026
    From Newsgroup: comp.lang.c++

    On 10/23/2026 8:39 PM, Lawrence DrCOOliveiro wrote:
    [...]

    I was in the linux world for a whiel, along with solaris, etc. But
    Windows, oh my. vcpkg is a big turn.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 05:56:28 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 19:51:23 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 8:39 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 16:58:04 -0700, Chris M. Thomasson wrote:

    Keeping them up to date is, afaict, manual.

    In the Linux world, we have rCLdevelopmentrCY packages versus rCLruntimerCY >> packages.

    The development package contains the source includes, pkg-config
    info etc. The runtime version includes the actual shared library.
    So your built package has a dependency on the latter; when a user
    tries to install your package, it should automatically pull in the
    latter as necessary.

    Example from my system:

    lrwxrwxrwx 1 root root 13 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so -> libcairo.so.2
    lrwxrwxrwx 1 root root 21 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so.2 -> libcairo.so.2.11804.4
    -rw-r--r-- 1 root root 1366728 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so.2.11804.4

    Where did these come from?

    root@theon:~ # dpkg-query -S /usr/lib/x86_64-linux-gnu/libcairo.so.2
    libcairo2:amd64: /usr/lib/x86_64-linux-gnu/libcairo.so.2

    root@theon:~ # dpkg-query -S /usr/lib/x86_64-linux-gnu/libcairo.so
    libcairo2-dev:amd64: /usr/lib/x86_64-linux-gnu/libcairo.so

    Notice how the development library is not versioned, but is just a
    symlink to a versioned library.

    The runtime library is always versioned. This allows multiple
    versions of the library to be present at once, with some older
    packages, that havenrCOt been rebuilt, still depending on an older
    version, while up-to-date packages make use of the newer version.

    I was in the linux world for a whiel, along with solaris, etc. But
    Windows, oh my. vcpkg is a big turn.

    Windows isnrCOt even in the same league, is it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.folklore.computers on Tue Oct 27 06:08:59 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 19:14:57 -0700, Lars Poulsen wrote:

    Processes are almost self-contained virtual machines. Unix has one
    of the cleanest implementations around, and the fork() system call
    combined with copy-on-write is very elegant. None of the other
    operating system I have worked with have anything remotely like it.
    VMS was also quite elegant, but so different that I think it would
    be impossible to simulate one on the other (in either direction).

    Remember that copy-on-write was a later addition. Early Unix systems
    had much more primitive memory management than VMS. But they did catch
    up.

    VMS had this odd distinction between rCLsubprocessesrCY and rCLdetached processesrCY. You didnrCOt need special privilege to create the former
    (though it was limited by a process quota), but you did for the
    latter. And there were the idiosyncrasies of the rCLUICrCY business, which
    were a hangover from RSX-11.

    Why were login processes initially created under a UIC of [10,40]? (In
    octal, no less.)

    The one clever thing about VMS that I miss most on Linux systems was
    the terminal driver. The functionality of that was a wonder to behold.

    Threads are much simpler. Multiple strands of execution in a shared
    address space. All the language needs to do is provide one shared
    vocabulary to allow code portability.

    There are some gotchas. Threads can be a notorious source of
    hard-to-find bugs. Note how the POSIX spec defines rCLcancellation
    pointsrCY, which are a detailed list of system service/userland API
    calls where the thread could potentially get force-terminated on
    request from another process thread, as opposed to having it happen at
    any time.

    To me it is obvious that threads can and should be standardized, while processes are generally not portable.

    What about a system like Linux, where the two are really just points
    on a spectrum of possibilities?

    <https://manpages.debian.org/clone(2)> is the underlying common kernel
    call that is used to implement both fork(2) and pthread_create(3) on
    Linux.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 10:22:55 2026
    From Newsgroup: comp.lang.c++

    On Tue, 27 Oct 2026 09:06:26 +0100
    David Brown <david.brown@hesbynett.no> wrote:
    On 27/10/2026 04:44, Chris M. Thomasson wrote:
    On 10/25/2026 2:45 AM, David Brown wrote:

    No one is suggesting that the threads themselves are implemented
    in pure, standard, portable C++.a You need an underlying OS or
    support of some sort if you are going to have preemptable threads.
    It's the same principle as IO and file access.

    But the difference between threads and processes is very simple
    from the viewpoint of C and C++.a Suppose you have a global (i.e.,
    external linkage) variable :

    aaaaaint x;

    Two threads that have "int a = x;" see the same "x" (ignoring data
    races and synchronisation).a Two processes see completely
    different "x".[...]

    Bingo. So, trying to imply that system is something okay for multi process, well, good luck. Daft. C/C++ has no std way to deal with
    multi process. But, we can use C/C++ to program for it all day
    long. Interesting.

    There are, of course, languages and runtime systems that handle
    processes too. An obvious example is Python. But it does it using a significantly "thicker" abstraction layer, combined with a
    significant run-time system to manage it all. And as a programmer,
    you have to be aware that you can't access global data from different processes, in the way you can do from different threads - you can
    only use data that is explicitly shared, or of appropriate data
    structures (like the process-aware queues). Behind the scenes, there
    is a lot of work to pass and synchronise all this using named pipes, memmapped shared files, etc. While C++ programmers are used to there
    being a certain degree of "hidden work" (unlike in C, where work is
    much more explicit), this kind of thing is not at all a match for the
    C++ philosophy.

    And there are languages like Erlang that divide everything into micro-processes, and use the same mechanisms for controlling and
    passing data around regardless of whether this little processes are
    in the same thread, or different threads, different OS processes, or different computers. That works because there are very narrow and
    tightly controlled mechanisms for sharing data.

    Note that these are both languages that run on a VM, not compiled
    languages.

    What you wrote about Erlang resembles MPI, which of course is readily
    available for many compiled or jitted languages, including Fortran, C
    and C++.
    I tried to utilize MPI 20 years ago, but the thinking behind it is to
    different from mine, so I ran away in horror.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 10:40:00 2026
    From Newsgroup: comp.lang.c++

    In article <20261027102255.00006052@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Tue, 27 Oct 2026 09:06:26 +0100
    David Brown <david.brown@hesbynett.no> wrote:
    [snip]
    And there are languages like Erlang that divide everything into
    micro-processes, and use the same mechanisms for controlling and
    passing data around regardless of whether this little processes are
    in the same thread, or different threads, different OS processes, or
    different computers. That works because there are very narrow and
    tightly controlled mechanisms for sharing data.

    Note that these are both languages that run on a VM, not compiled
    languages.

    What you wrote about Erlang resembles MPI, which of course is readily >available for many compiled or jitted languages, including Fortran, C
    and C++.
    I tried to utilize MPI 20 years ago, but the thinking behind it is to >different from mine, so I ran away in horror.

    Erlang uses the "actor" model to represent concurrency; state is
    held by each actor, and actors communicate via message passing,
    potentially changing state in response to messages. This is a
    model for _concurrency_, in which multiple independent threads
    of execution are coordinated to some in a single system.

    One may think of MPI-style systems this way, but there's a
    subtle distinction. The typical use case for something like MPI
    is _parallel_ computation of a numerically intensive problem,
    where "neighbors" nodes need to occasionally share state; this
    is usually about _parallelism_; that is, simultaneity. While a
    concurrency primitive is _necessary_ to think about parallelism
    (and MPI can be used in that fashion), the two are distinct
    concepts that are often conflated. To paraphrase Rob Pike on
    it, concurrency is about dealing with multiple things at once,
    while parallelism is about doing lots of things at the same
    time.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 15:03:45 2026
    From Newsgroup: comp.lang.c++

    cross@spitfire.i.gajendra.net (Dan Cross) writes:
    In article <20261027102255.00006052@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Tue, 27 Oct 2026 09:06:26 +0100
    David Brown <david.brown@hesbynett.no> wrote:
    [snip]
    And there are languages like Erlang that divide everything into
    micro-processes, and use the same mechanisms for controlling and
    passing data around regardless of whether this little processes are
    in the same thread, or different threads, different OS processes, or
    different computers. That works because there are very narrow and
    tightly controlled mechanisms for sharing data.

    Note that these are both languages that run on a VM, not compiled
    languages.

    What you wrote about Erlang resembles MPI, which of course is readily >>available for many compiled or jitted languages, including Fortran, C
    and C++.
    I tried to utilize MPI 20 years ago, but the thinking behind it is to >>different from mine, so I ran away in horror.

    Erlang uses the "actor" model to represent concurrency; state is
    held by each actor, and actors communicate via message passing,
    potentially changing state in response to messages. This is a
    model for _concurrency_, in which multiple independent threads
    of execution are coordinated to some in a single system.

    Chorus (the microkernel) worked in a similar fashion. The
    microkernel coordinated between actors using message passing.

    The actors implemented the higher level operating system
    functionality. The Amadeus project, for example, implemented
    a version of unix on top of the microkernel using message
    passing between actors (The Object manager handled files and
    filesystems, the Process actor handled the POSIX process
    and thread (SVR4.2ES/MP threads) interfaces including fork,
    and light-weight processes that implemented threads, and
    the Streams actor provide system V streams support and
    networking.

    Unisys released the OS as part of their massively parallel
    OPUS computer system.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 08:57:08 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 13:10:46 -0600
    Blaine <cactus_DAC@yahoo.com> gabbled:
    boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 14:22:34 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
    The differences are utterly irrelevant when it comes to prividing a
    common
    API to the functionality but thank you for demonstrating you had no
    answer
    to my question.


    Ummm... It is relevant. Every process has a single thread of
    execution, but not all processes have multiple threads.

    No shit sherlock, thanks for the heads up. Your point is?

    Basically that methinks you insult too much. Your wisdom here isn't
    worth a sack of beans. I haven't learned one thing from you.

    Thats your problem, not mine.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 08:58:55 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 21:45:17 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 14:41:54 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:
    boltar@caprica.universe writes:
    C++ threading didn't have 3 level locking until 2017 making it
    effectively useless IMO. Perhaps that was down to the lowest common
    denominator called Windows.


    Mind defining your terminology? "3 level locking", in particular?

    If you have to ask....

    1. No lock
    2. Write lock - Read only access, writer blocked until all readers
    out of critic al section)
    3. Read-write lock - all threads other than the one in section block)


    Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
    time as conditional variables. 5 years before C++11.

    And unix got pthreads in 1995. Windows a decade late as usual.

    Not useless then, just less useful.


    I never ever used what you call "3 level locking", not even by mistake.
    But then, I don't write complicated apps on "big" computers day in day
    out.

    Fine, most people will never use it, but for certain things its vital.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 09:06:47 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 22:04:33 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:
    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.

    Rubbish, you clearly didn't bother to spend 2 mins googling.

    The problem with system() is not that. Often not even an efficiency.
    The problem with system() identified most easily if we ask ourself "Why
    do we want xyz in standard library?"

    The problem with system is its fire and forget - all you can do with it is collect its exit code when its done. You can't communicate with it via
    pipes, you can't control it via signals (well, not easily), you can't set its process group, tty and on and on. Oh, and it also fires up the default shell to do the actual execution making it hideously inefficient. No serious unix dev uses system() unless thay have absolutely no choice or it really is a case of "go run this, I don't care what happens".


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 09:08:44 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 22:09:01 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    win32 can't do fork() making it effectively a totally useless API for
    a lot of multiprocess development. Creating a brand new process is
    fine if you don't need any complicated shared state such as when
    kicking off something on the command line or creating a pipe
    (something else win32 is shit at) but thats about it.


    You are clueless about Windows. That's o.k.
    Your pretense that you know something about it is not o.k.
    In that regard you are not better than LDO.

    OK, whats the windows API call thats the equivalent of fork()? I'm not
    talking about CreateProcessA() which doesn't even come close.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.c++,alt.folklore.computers on Wed Oct 28 09:09:32 2026
    From Newsgroup: comp.lang.c++

    On Mon, 26 Oct 2026 13:19:14 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/26/2026 9:19 AM, boltar@caprica.universe wrote:
    I'd be interested how you'd implement fork() using that method given you
    need to copy the state of all file descriptors, heap, stack and global
    memory, current working directory, enviroment variables and a ton of other >> things I can't remember without googling.


    Why even do that? Sigh.

    Why don't you go and find out and educate yourself.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 08:39:57 2026
    From Newsgroup: comp.lang.c++

    boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 13:10:46 -0600
    Blaine <cactus_DAC@yahoo.com> gabbled:
    boltar@caprica.universe wrote:
    On Sun, 25 Oct 2026 14:22:34 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
    The differences are utterly irrelevant when it comes to prividing a >>>>> common
    API to the functionality but thank you for demonstrating you had no >>>>> answer
    to my question.


    Ummm... It is relevant. Every process has a single thread of
    execution, but not all processes have multiple threads.

    No shit sherlock, thanks for the heads up. Your point is?

    Basically that methinks you insult too much. Your wisdom here isn't
    worth a sack of beans. I haven't learned one thing from you.

    Thats your problem, not mine.

    I'm sorry you are unable to do a better job. Oh well, you just suck and
    can't do any better, so it's on me.
    --
    Sometimes I just feel like I need to get away
    A place where I can be by myself, all alone
    I kinda lay down in the back yard
    Watch the leaves fall down on my face
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Blaine@cactus_DAC@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 09:47:16 2026
    From Newsgroup: comp.lang.c++

    boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 13:03:25 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/26/2026 3:01 AM, boltar@caprica.universe wrote:
    Creating a brand new process is fine if
    you don't need any complicated shared state such as when kicking off
    something
    on the command line or creating a pipe (something else win32 is shit
    at) but
    thats about it.


    Shared state? Just use memory mapped files. You don't need
    pipes/sockets etc. You need to know how to properly sync things.

    Oh really? So you receive an incoming connection to a socket via an
    accept()
    call. In unix you can fork() at that point so the connecting client has a server process all to itself with all the state instantly copied from the parent process. HOw do you mimic that in windows? Start the server process from scratch and pass it a ton of state via the command line or using some roll-your-own shared memory nonsense? Give me a break. I guess in
    windows it
    spawns a thread leading to the issue of a single thread crashing
    bringing down
    the entire application - something multiprocess completely avoids.

    Innocent like a lamb for me.
    Just make a call to malloc() and probe the GarbageCollector. You've got
    it all wrong, stupid.
    --
    Sometimes I just feel like I need to get away
    A place where I can be by myself, all alone
    I kinda lay down in the back yard
    Watch the leaves fall down on my face
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 21:47:46 2026
    From Newsgroup: comp.lang.c++

    On Wed, 28 Oct 2026 09:06:47 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 22:04:33 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:
    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.

    Rubbish, you clearly didn't bother to spend 2 mins googling.

    The problem with system() is not that. Often not even an efficiency.
    The problem with system() identified most easily if we ask ourself
    "Why do we want xyz in standard library?"

    The problem with system is its fire and forget - all you can do with
    it is collect its exit code when its done. You can't communicate with
    it via pipes, you can't control it via signals (well, not easily),
    you can't set its process group, tty and on and on.

    Actually, if you are creative enough you can do most of the
    above-mentioned things. Of course, what you can and what you can't do
    depends on capabilities of your default shell.
    And of course the way by which you achieve your goals via system() is
    VERY OS-dependent.

    Oh, and it also
    fires up the default shell to do the actual execution making it
    hideously inefficient.

    It matters only when the work delegated to sub-process is both brief and
    done very often.

    No serious unix dev uses system() unless thay
    have absolutely no choice or it really is a case of "go run this, I
    don't care what happens".


    I can't argue about it. Supposedly, it depends on definition of "serious
    unix dev". In my book, serious dev is one who knows to peek
    correctly-sized tool to the job rather than one who always uses the
    most efficient tool.
    But that's is off topic.

    Pay attention that I agree with you that system() is not suitable as
    The Only standard way of support of multiple processes in C++ standard
    library, even if my reasons for that are different from yours.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 22:05:58 2026
    From Newsgroup: comp.lang.c++

    On Wed, 28 Oct 2026 09:08:44 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 22:09:01 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    win32 can't do fork() making it effectively a totally useless API
    for a lot of multiprocess development. Creating a brand new
    process is fine if you don't need any complicated shared state
    such as when kicking off something on the command line or creating
    a pipe (something else win32 is shit at) but thats about it.


    You are clueless about Windows. That's o.k.
    Your pretense that you know something about it is not o.k.
    In that regard you are not better than LDO.

    OK, whats the windows API call thats the equivalent of fork()? I'm not talking about CreateProcessA() which doesn't even come close.


    There is no equivalent for fork(). But nearly all things that Posix
    devs achieve by fork() followed by one or another magic incantation and
    then followed by exec() can be achived on Windows as well, typically by
    means of one or another magic flag in parameters of CreateProcess or
    of one of it's more complicated cousins (CreateProcessAsUser, CreateProcessWithLogon, CreateProcessWithToken, may be others). These
    things never fascinated me, so I am not an expert.

    Now, there were cases where Unix programmers used fork() without
    following it by exec(), but I would think that in the recent 25-30 years
    such programming patterns are discouraged in favor of threads.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.c++,alt.folklore.computers on Wed Oct 28 14:10:48 2026
    From Newsgroup: comp.lang.c++

    On 10/28/2026 2:09 AM, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 13:19:14 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/26/2026 9:19 AM, boltar@caprica.universe wrote:
    I'd be interested how you'd implement fork() using that method given you >>> need to copy the state of all file descriptors, heap, stack and
    global memory, current working directory, enviroment variables and a
    ton of other
    things I can't remember without googling.


    Why even do that? Sigh.

    Why don't you go and find out and educate yourself.


    I know how to use windows, and fork is the last thing on my mind.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 00:06:45 2026
    From Newsgroup: comp.lang.c++

    On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 21:45:17 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 16:16:46 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 14:41:54 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:
    boltar@caprica.universe writes:
    C++ threading didn't have 3 level locking until 2017 making it
    effectively useless IMO. Perhaps that was down to the lowest
    common denominator called Windows.


    Mind defining your terminology? "3 level locking", in
    particular?

    If you have to ask....

    1. No lock
    2. Write lock - Read only access, writer blocked until all readers
    out of critic al section)
    3. Read-write lock - all threads other than the one in section
    block)

    Windows got Slim Reader/Writer Locks in Vista (2006-11) at the same
    time as conditional variables. 5 years before C++11.

    And unix got pthreads in 1995. Windows a decade late as usual.


    That's like if I'd say that Linux is 33 years (and counting) late
    because it has no QueueUserAPC(). Of course, I am smarter than saying
    such nonsense.

    More relevantly, Windows (Win32) has preemptive kernel-scheduled threads
    + assortment of synchronization primitives since very beginning (1993)
    - ahead of many Unixen and behind some of them. Certainly ahead of
    Posix standardisation of threads.






    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 16:16:34 2026
    From Newsgroup: comp.lang.c++

    On Wed, 28 Oct 2026 22:05:58 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 28 Oct 2026 09:08:44 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Mon, 26 Oct 2026 22:09:01 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 10:01:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    win32 can't do fork() making it effectively a totally useless API
    for a lot of multiprocess development. Creating a brand new
    process is fine if you don't need any complicated shared state
    such as when kicking off something on the command line or creating
    a pipe (something else win32 is shit at) but thats about it.


    You are clueless about Windows. That's o.k.
    Your pretense that you know something about it is not o.k.
    In that regard you are not better than LDO.

    OK, whats the windows API call thats the equivalent of fork()? I'm not
    talking about CreateProcessA() which doesn't even come close.


    There is no equivalent for fork(). But nearly all things that Posix
    devs achieve by fork() followed by one or another magic incantation and
    then followed by exec() can be achived on Windows as well, typically by
    means of one or another magic flag in parameters of CreateProcess or
    of one of it's more complicated cousins (CreateProcessAsUser, >CreateProcessWithLogon, CreateProcessWithToken, may be others). These
    things never fascinated me, so I am not an expert.

    Now, there were cases where Unix programmers used fork() without
    following it by exec(), but I would think that in the recent 25-30 years
    such programming patterns are discouraged in favor of threads.

    Depends how much resilience you need. If the child process needs the state
    of the parent but doesn't need to interact with it or any of the other child processes much if at all and you're not creating dozens of them a second then why would you use a thread with all the associated hassle of critical section requirements, deadlocks, potential race conditions and one thread crashing killing the whole application?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 16:22:29 2026
    From Newsgroup: comp.lang.c++

    On Thu, 29 Oct 2026 00:06:45 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    And unix got pthreads in 1995. Windows a decade late as usual.


    That's like if I'd say that Linux is 33 years (and counting) late
    because it has no QueueUserAPC(). Of course, I am smarter than saying
    such nonsense.

    More relevantly, Windows (Win32) has preemptive kernel-scheduled threads
    + assortment of synchronization primitives since very beginning (1993)
    - ahead of many Unixen and behind some of them. Certainly ahead of
    Posix standardisation of threads.

    Wow, pre-emptive multitasking in 1993. Incredible technology!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 22:39:22 2026
    From Newsgroup: comp.lang.c++

    On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Thu, 29 Oct 2026 00:06:45 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    And unix got pthreads in 1995. Windows a decade late as usual.


    That's like if I'd say that Linux is 33 years (and counting) late
    because it has no QueueUserAPC(). Of course, I am smarter than saying
    such nonsense.

    More relevantly, Windows (Win32) has preemptive kernel-scheduled
    threads
    + assortment of synchronization primitives since very beginning
    (1993)
    - ahead of many Unixen and behind some of them. Certainly ahead of
    Posix standardisation of threads.

    Wow, pre-emptive multitasking in 1993. Incredible technology!


    Not just preemptive multitasking between processes, but
    kernel-scheduled threads within each process as well.
    Not a novel idea, but the one that eventually won over all others.
    In 1993 it was already obvious that it is going to win, but in
    1988-1989, when development started, it was less trivial.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 23:07:58 2026
    From Newsgroup: comp.lang.c++

    On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Wed, 28 Oct 2026 14:09:32 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 22:04:33 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:
    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.

    Rubbish, you clearly didn't bother to spend 2 mins googling.

    The problem with system() is not that. Often not even an
    efficiency. The problem with system() identified most easily if
    we ask ourself "Why do we want xyz in standard library?"

    The problem with system is its fire and forget - all you can do
    with it is collect its exit code when its done. You can't
    communicate with it via pipes, you can't control it via signals
    (well, not easily), you can't set its

    process group, tty and on and on. Oh, and it also fires up the
    default shell
    to
    do the actual execution making it hideously inefficient. No
    serious unix dev uses system() unless thay have absolutely no
    choice or it really is a case of

    "go run this, I don't care what happens".



    Right. std::system, at least when I use it, makes the caller block
    until the process is done.

    Thats true. Its been so long since I used it I'd forgotten about
    that. Makes it even less useful.


    Does it block when your command processor is bash and your command
    string is "my_subprocess &"?
    Does it block when your command processor is cmd.exe and your command
    string "start my_subprocess" or "start /b my_subprocess"?

    I almost certainly tried both in the past, but don't remember what
    happens in each case. My expectations are that in both cases
    caller blocked only briefly. It is not blocked until the finish
    my_subprocess.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 22:25:40 2026
    From Newsgroup: comp.lang.c++

    Michael S <already5chosen@yahoo.com> writes:
    On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Thu, 29 Oct 2026 00:06:45 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    And unix got pthreads in 1995. Windows a decade late as usual.


    That's like if I'd say that Linux is 33 years (and counting) late
    because it has no QueueUserAPC(). Of course, I am smarter than saying
    such nonsense.

    More relevantly, Windows (Win32) has preemptive kernel-scheduled
    threads
    + assortment of synchronization primitives since very beginning
    (1993)
    - ahead of many Unixen and behind some of them. Certainly ahead of
    Posix standardisation of threads.

    Wow, pre-emptive multitasking in 1993. Incredible technology!


    Not just preemptive multitasking between processes, but
    kernel-scheduled threads within each process as well.
    Not a novel idea, but the one that eventually won over all others.
    In 1993 it was already obvious that it is going to win, but in
    1988-1989, when development started, it was less trivial.


    The thread design for SVR4 Unix started in the late 80s and
    released in 1993.

    Digital published "Evolving the UNIX System Interface to
    Support Multithreaded Programs" September 28, 1987.
    (Paul R. McJones and Garret F. Swart).

    The "The Topaz Operating System User's Guide" in that document
    describes the thread interface. (DIGITAL Systems Research
    Center operating system) for both VAX/Ultrix and the Firefly/Taos implementation.

    Here's a link to the paper published a couple years later:

    https://softwarepreservation.computerhistory.org/modula2+/doc/McJones_Swart-Evolving-1989.pdf

    And here's a link to the full technical report #21 (including the manual)

    https://ftp.zx.net.nz/pub/archive/gatekeeper.dec.com/pub/DEC/SRC/research-reports/SRC-021.pdf
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 22:26:40 2026
    From Newsgroup: comp.lang.c++

    Michael S <already5chosen@yahoo.com> writes:
    On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Wed, 28 Oct 2026 14:09:32 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 22:04:33 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:
    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.

    Rubbish, you clearly didn't bother to spend 2 mins googling.

    The problem with system() is not that. Often not even an
    efficiency. The problem with system() identified most easily if
    we ask ourself "Why do we want xyz in standard library?"

    The problem with system is its fire and forget - all you can do
    with it is collect its exit code when its done. You can't
    communicate with it via pipes, you can't control it via signals
    (well, not easily), you can't set its

    process group, tty and on and on. Oh, and it also fires up the
    default shell
    to
    do the actual execution making it hideously inefficient. No
    serious unix dev uses system() unless thay have absolutely no
    choice or it really is a case of

    "go run this, I don't care what happens".



    Right. std::system, at least when I use it, makes the caller block
    until the process is done.

    Thats true. Its been so long since I used it I'd forgotten about
    that. Makes it even less useful.


    Does it block when your command processor is bash and your command
    string is "my_subprocess &"?

    You might need to do 'nohup my_subprocess &' if my_subprocess
    doesn't intercept SIGHUP.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 00:54:34 2026
    From Newsgroup: comp.lang.c++

    On Thu, 29 Oct 2026 22:26:40 GMT
    scott@slp53.sl.home (Scott Lurndal) wrote:

    Michael S <already5chosen@yahoo.com> writes:
    On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Wed, 28 Oct 2026 14:09:32 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 22:04:33 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:
    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.

    Rubbish, you clearly didn't bother to spend 2 mins googling.

    The problem with system() is not that. Often not even an
    efficiency. The problem with system() identified most easily if
    we ask ourself "Why do we want xyz in standard library?"

    The problem with system is its fire and forget - all you can do
    with it is collect its exit code when its done. You can't
    communicate with it via pipes, you can't control it via signals
    (well, not easily), you can't set its

    process group, tty and on and on. Oh, and it also fires up the
    default shell
    to
    do the actual execution making it hideously inefficient. No
    serious unix dev uses system() unless thay have absolutely no
    choice or it really is a case of

    "go run this, I don't care what happens".



    Right. std::system, at least when I use it, makes the caller block
    until the process is done.

    Thats true. Its been so long since I used it I'd forgotten about
    that. Makes it even less useful.


    Does it block when your command processor is bash and your command
    string is "my_subprocess &"?

    You might need to do 'nohup my_subprocess &' if my_subprocess
    doesn't intercept SIGHUP.


    You are likely right. Otherwise OS will kill my_subprocess at about the
    same time the caller of system() gets control back.
    I would not figure it out myself.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 02:10:59 2026
    From Newsgroup: comp.lang.c++

    In article <EJPES.62185$BaS5.30884@fx35.iad>,
    Scott Lurndal <slp53@pacbell.net> wrote:
    Michael S <already5chosen@yahoo.com> writes:
    On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Thu, 29 Oct 2026 00:06:45 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    And unix got pthreads in 1995. Windows a decade late as usual.


    That's like if I'd say that Linux is 33 years (and counting) late
    because it has no QueueUserAPC(). Of course, I am smarter than saying
    such nonsense.

    More relevantly, Windows (Win32) has preemptive kernel-scheduled
    threads
    + assortment of synchronization primitives since very beginning
    (1993)
    - ahead of many Unixen and behind some of them. Certainly ahead of
    Posix standardisation of threads.

    Wow, pre-emptive multitasking in 1993. Incredible technology!


    Not just preemptive multitasking between processes, but
    kernel-scheduled threads within each process as well.
    Not a novel idea, but the one that eventually won over all others.
    In 1993 it was already obvious that it is going to win, but in
    1988-1989, when development started, it was less trivial.

    The thread design for SVR4 Unix started in the late 80s and
    released in 1993.

    Digital published "Evolving the UNIX System Interface to
    Support Multithreaded Programs" September 28, 1987.
    (Paul R. McJones and Garret F. Swart).

    The "The Topaz Operating System User's Guide" in that document
    describes the thread interface. (DIGITAL Systems Research
    Center operating system) for both VAX/Ultrix and the Firefly/Taos >implementation.

    Here's a link to the paper published a couple years later:

    https://softwarepreservation.computerhistory.org/modula2+/doc/McJones_Swart-Evolving-1989.pdf

    And here's a link to the full technical report #21 (including the manual)

    https://ftp.zx.net.nz/pub/archive/gatekeeper.dec.com/pub/DEC/SRC/research-reports/SRC-021.pdf

    Speaking of.... I have a distinct memory of reading a paper
    called something like, "fork mixed with threads considered
    harmful"; I could have sworn it was by Luca Cardelli, but I do
    not think that is correct, nor can I find it.... At least the
    Gatekeeper archive of SRC reports was mirrored. Maybe it's in
    there (it's not the evolving paper, though that touches on the
    issues).

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 02:22:43 2026
    From Newsgroup: comp.lang.c++

    In article <20261030005434.00005458@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Thu, 29 Oct 2026 22:26:40 GMT
    scott@slp53.sl.home (Scott Lurndal) wrote:

    Michael S <already5chosen@yahoo.com> writes:
    On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Wed, 28 Oct 2026 14:09:32 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 22:04:33 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:
    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.

    Rubbish, you clearly didn't bother to spend 2 mins googling.

    The problem with system() is not that. Often not even an
    efficiency. The problem with system() identified most easily if
    we ask ourself "Why do we want xyz in standard library?"

    The problem with system is its fire and forget - all you can do
    with it is collect its exit code when its done. You can't
    communicate with it via pipes, you can't control it via signals
    (well, not easily), you can't set its

    process group, tty and on and on. Oh, and it also fires up the
    default shell
    to
    do the actual execution making it hideously inefficient. No
    serious unix dev uses system() unless thay have absolutely no
    choice or it really is a case of

    "go run this, I don't care what happens".



    Right. std::system, at least when I use it, makes the caller block
    until the process is done.

    Thats true. Its been so long since I used it I'd forgotten about
    that. Makes it even less useful.


    Does it block when your command processor is bash and your command
    string is "my_subprocess &"?

    You might need to do 'nohup my_subprocess &' if my_subprocess
    doesn't intercept SIGHUP.


    You are likely right. Otherwise OS will kill my_subprocess at about the
    same time the caller of system() gets control back.
    I would not figure it out myself.

    Only if you intended to close the TTY the programs were started
    on. Otherwise, I don't see why it would be necessary:

    ```
    term% cat a.c
    #include <stdio.h>
    #include <stdlib.h>
    #include <time.h>
    #include <unistd.h>

    int
    main(void)
    {
    struct tm *t;
    time_t now = time(NULL);
    printf("Starting child, time is %s", asctime(gmtime(&now)));
    sleep(5);
    now = time(NULL);
    printf("Bye bye, now is %s", asctime(gmtime(&now)));
    }
    term% cat b.c
    #include <stdio.h>
    #include <stdlib.h>
    #include <time.h>
    #include <unistd.h>

    int
    main(void)
    {
    time_t now = time(NULL);
    printf("Parent starting, time is %s", asctime(gmtime(&now)));
    system("./a &");
    printf("./a started in background\n");
    sleep(2);
    now = time(NULL);
    printf("Ahhh!!! time is %s", asctime(gmtime(&now)));
    return 0;
    }
    term% make a
    cc -O2 -pipe -o a a.c
    term% make b
    cc -O2 -pipe -o b b.c
    term% ./b
    Parent starting, time is Fri Oct 30 02:21:06 2026
    ./a started in background
    Starting child, time is Fri Oct 30 02:21:06 2026
    Ahhh!!! time is Fri Oct 30 02:21:08 2026
    term% Bye bye, now is Fri Oct 30 02:21:11 2026
    ```

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Smith@invalid@invalid.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust on Fri Oct 30 05:04:30 2026
    From Newsgroup: comp.lang.c++

    On 14/10/2026 05:18, Lynn McGuire wrote:
    rCLThe end of software secrecy is almost upon us. The death of closed source, and the final triumph of open source. rCY -Eric S. Raymond.


    What's the situation re C++ 26?

    <https://elsolitario.org/en/2026/10/26/according-to-seacord-cpp26-fails-dis-ballot-12-of-20/>

    Any progress?




    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 10:59:00 2026
    From Newsgroup: comp.lang.c++

    On Fri, 30 Oct 2026 02:22:43 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:

    In article <20261030005434.00005458@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Thu, 29 Oct 2026 22:26:40 GMT
    scott@slp53.sl.home (Scott Lurndal) wrote:

    Michael S <already5chosen@yahoo.com> writes:
    On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Wed, 28 Oct 2026 14:09:32 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/28/2026 2:06 AM, boltar@caprica.universe wrote:
    On Mon, 26 Oct 2026 22:04:33 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 26 Oct 2026 09:51:51 -0000 (UTC)
    boltar@caprica.universe wrote:
    Go ahead and remain clueless.



    system() can do most of the same things as spawn() family.

    Rubbish, you clearly didn't bother to spend 2 mins googling.

    The problem with system() is not that. Often not even an
    efficiency. The problem with system() identified most
    easily if we ask ourself "Why do we want xyz in standard
    library?"

    The problem with system is its fire and forget - all you can
    do with it is collect its exit code when its done. You can't
    communicate with it via pipes, you can't control it via
    signals (well, not easily), you can't set its

    process group, tty and on and on. Oh, and it also fires up
    the default shell
    to
    do the actual execution making it hideously inefficient. No
    serious unix dev uses system() unless thay have absolutely no
    choice or it really is a case of

    "go run this, I don't care what happens".



    Right. std::system, at least when I use it, makes the caller
    block until the process is done.

    Thats true. Its been so long since I used it I'd forgotten about
    that. Makes it even less useful.


    Does it block when your command processor is bash and your command
    string is "my_subprocess &"?

    You might need to do 'nohup my_subprocess &' if my_subprocess
    doesn't intercept SIGHUP.


    You are likely right. Otherwise OS will kill my_subprocess at about
    the same time the caller of system() gets control back.
    I would not figure it out myself.

    Only if you intended to close the TTY the programs were started
    on. Otherwise, I don't see why it would be necessary:

    What happens when caller is GUI-style application?


    ```
    term% cat a.c
    #include <stdio.h>
    #include <stdlib.h>
    #include <time.h>
    #include <unistd.h>

    int
    main(void)
    {
    struct tm *t;
    time_t now = time(NULL);
    printf("Starting child, time is %s", asctime(gmtime(&now)));
    sleep(5);
    now = time(NULL);
    printf("Bye bye, now is %s", asctime(gmtime(&now)));
    }
    term% cat b.c
    #include <stdio.h>
    #include <stdlib.h>
    #include <time.h>
    #include <unistd.h>

    int
    main(void)
    {
    time_t now = time(NULL);
    printf("Parent starting, time is %s", asctime(gmtime(&now)));
    system("./a &");
    printf("./a started in background\n");
    sleep(2);
    now = time(NULL);
    printf("Ahhh!!! time is %s", asctime(gmtime(&now)));
    return 0;
    }
    term% make a
    cc -O2 -pipe -o a a.c
    term% make b
    cc -O2 -pipe -o b b.c
    term% ./b
    Parent starting, time is Fri Oct 30 02:21:06 2026
    ./a started in background
    Starting child, time is Fri Oct 30 02:21:06 2026
    Ahhh!!! time is Fri Oct 30 02:21:08 2026
    term% Bye bye, now is Fri Oct 30 02:21:11 2026
    ```

    - Dan C.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From cross@cross@spitfire.i.gajendra.net (Dan Cross) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 11:25:01 2026
    From Newsgroup: comp.lang.c++

    In article <20261030105900.000020ce@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Fri, 30 Oct 2026 02:22:43 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:

    In article <20261030005434.00005458@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    On Thu, 29 Oct 2026 22:26:40 GMT
    scott@slp53.sl.home (Scott Lurndal) wrote:

    Michael S <already5chosen@yahoo.com> writes:
    On Thu, 29 Oct 2026 16:20:39 -0000 (UTC)
    [snip]
    Does it block when your command processor is bash and your command
    string is "my_subprocess &"?

    You might need to do 'nohup my_subprocess &' if my_subprocess
    doesn't intercept SIGHUP.


    You are likely right. Otherwise OS will kill my_subprocess at about
    the same time the caller of system() gets control back.
    I would not figure it out myself.

    Only if you intended to close the TTY the programs were started
    on. Otherwise, I don't see why it would be necessary:

    What happens when caller is GUI-style application?

    That depends on a number of factors, but basically, "it does the
    same thing". Why would it be any different?

    SIGHUP is the "hangup" signal, and _usually_ generated by the
    kernel when a process loses its controlling terminal, though it
    _can_ be sent from the command line (or a program) using the
    `kill` command or one of its many imitators (basically, anything
    that invokes `raise()` or the `kill()` system call).

    The classic example of its use was a dial-in terminal line that
    recognized modem status and reacted to a "carrier detect" signal
    dropping; the kernel would clean up by SIGHUP'ing the process
    group of anything associated with that terminal; one can see
    this readily in early Unix kernel sources. This is a reason why
    SIGHUP is one of the few signals a shell will actually honor.

    Nowadays, this most often happens when an interactive session
    associated with a pseudoterminal is closed; this could be window
    in a terminal emulator program, or it could be a network login
    via e.g. `ssh` that closes.

    For programs that are not associated with a TTY at all, this
    won't happen; this is why traditionally Unix daemons often
    overloaded SIGHUP to force reloading a config file or similar:
    since daemons are not generally associated with user ttys (or
    often any TTY at all, including the console), the kernel will
    never automatically send them a SIGHUP to terminate, so it's a
    "safe" signal to pick for administrative control.

    Crucially, using `system()` to invoke a program, even one that
    is backgrounded, does not usually allocate a new terminal, nor
    does it necessarily close one (though I suppose one could use it
    to invoke something like, `kill -9 -1` to zap all of one's
    processes; you could even background that if you wanted, but
    that seems silly).

    GUI programs are no different in this regard. Many of them may
    not even be associated with a tty device at all, and may receive
    their "session has ended" notification some other way.

    So I go back to my original statement, "only if you intended to
    close the TTY the programs were started on." IF you intend to
    start some long-running program in the background and you won't
    stay logged in after doing that, then sure, use `nohup`. But
    if you don't care about that, then you don't need to bother.
    The OS will not kill your program when the shell started by
    `system` exits or anything; nor will the shell itself.

    - Dan C.

    ```
    term% cat a.c
    #include <stdio.h>
    #include <stdlib.h>
    #include <time.h>
    #include <unistd.h>

    int
    main(void)
    {
    time_t now = time(NULL);
    printf("Starting child, time is %s", asctime(gmtime(&now)));
    sleep(5);
    now = time(NULL);
    printf("Bye bye, now is %s", asctime(gmtime(&now)));
    }
    term% cat b.c
    #include <stdio.h>
    #include <stdlib.h>
    #include <time.h>
    #include <unistd.h>

    int
    main(void)
    {
    time_t now = time(NULL);
    printf("Parent starting, time is %s", asctime(gmtime(&now)));
    system("./a &");
    printf("./a started in background\n");
    sleep(2);
    now = time(NULL);
    printf("Ahhh!!! time is %s", asctime(gmtime(&now)));
    return 0;
    }
    term% make a
    cc -O2 -pipe -o a a.c
    term% make b
    cc -O2 -pipe -o b b.c
    term% ./b
    Parent starting, time is Fri Oct 30 02:21:06 2026
    ./a started in background
    Starting child, time is Fri Oct 30 02:21:06 2026
    Ahhh!!! time is Fri Oct 30 02:21:08 2026
    term% Bye bye, now is Fri Oct 30 02:21:11 2026
    ```
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 11:25:45 2026
    From Newsgroup: comp.lang.c++

    On Thu, 29 Oct 2026 22:39:22 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Thu, 29 Oct 2026 16:22:29 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Thu, 29 Oct 2026 00:06:45 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 28 Oct 2026 08:58:55 -0000 (UTC)
    boltar@caprica.universe wrote:
    And unix got pthreads in 1995. Windows a decade late as usual.


    That's like if I'd say that Linux is 33 years (and counting) late
    because it has no QueueUserAPC(). Of course, I am smarter than saying
    such nonsense.

    More relevantly, Windows (Win32) has preemptive kernel-scheduled
    threads
    + assortment of synchronization primitives since very beginning
    (1993)
    - ahead of many Unixen and behind some of them. Certainly ahead of
    Posix standardisation of threads.

    Wow, pre-emptive multitasking in 1993. Incredible technology!


    Not just preemptive multitasking between processes, but
    kernel-scheduled threads within each process as well.
    Not a novel idea, but the one that eventually won over all others.
    In 1993 it was already obvious that it is going to win, but in
    1988-1989, when development started, it was less trivial.

    Implementing threads is trivial compared to implementing multi processes with shared memory. Adding them to a pre-existing kernel might be tricky but when you're building one from scratch as per NT then its hardly a big deal.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 15:23:57 2026
    From Newsgroup: comp.lang.c++

    On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) wrote:


    The OS will not kill your program when the shell started by
    `system` exits or anything;


    Good to know.

    nor will the shell itself.

    That part I guessed myself.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 16:07:49 2026
    From Newsgroup: comp.lang.c++

    On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <20261030105900.000020ce@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    Only if you intended to close the TTY the programs were started
    on. Otherwise, I don't see why it would be necessary:

    What happens when caller is GUI-style application?

    That depends on a number of factors, but basically, "it does the
    same thing". Why would it be any different?

    Windows treats GUI apps entirely differently to console ones so a Windows
    dev might not appreciate that on unix there is no demarcation - a GUI app simply has a network connection to the X server and it can either sit in
    an event loop waiting for events - as per a windows main thread - or go do other things and periodically check the X event list.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 20:37:14 2026
    From Newsgroup: comp.lang.c++

    On 10/30/26 17:07, boltar@caprica.universe wrote:
    On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <20261030105900.000020ce@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    Only if you intended to close the TTY the programs were started
    on. Otherwise, I don't see why it would be necessary:

    What happens when caller is GUI-style application?

    That depends on a number of factors, but basically, "it does the
    same thing". Why would it be any different?

    Windows treats GUI apps entirely differently to console ones so a Windows
    dev might not appreciate that on unix there is no demarcation - a GUI app simply has a network connection to the X server and it can either sit in
    an event loop waiting for events - as per a windows main thread - or go do other things and periodically check the X event list.


    That's where threads are useful: The GUI is one thread, and the "other
    things" are in one or more other threads. There are altogether too many programs that hang the GUI while "other things" are going on. That
    should never happen!

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 22:35:05 2026
    From Newsgroup: comp.lang.c++

    On Fri, 30 Oct 2026 20:37:14 +0100, Jeroen Belleman wrote:

    That's where threads are useful: The GUI is one thread, and the
    "other things" are in one or more other threads. There are
    altogether too many programs that hang the GUI while "other things"
    are going on. That should never happen!

    Back in the 1990s, threading was seen as the answer to everything.
    Some even tried multithreaded GUIs.

    The trouble with threading is its rCLdefault-shared-everythingrCY model,
    as opposed to separate processes, which are rCLdefault-shared-nothingrCY.
    It is all too easy to forget to synchronize access to shared objects,
    lock things properly etc, and end up with hard-to-diagnose bugs that
    tend to hide themselves when you try to go look for them (see
    rCLHeisenbugrCY).

    The trend nowadays is to revive the old coroutine concept, in a new
    guise called rCLstacklessrCY coroutines. These give you support for async operations, but with transfers of control being made explicit at
    rCLawaitrCY points, rather than unpredictably as with full preemptive threading. This greatly reduces the opportunity for race conditions.

    Credit to Microsoft for pioneering this, but nowadays you see the idea
    popping up in JavaScript and Python and who knows where else.

    Threading is still definitely useful, mainly for performance, where
    the bottleneck is in CPU usage. But if a program is spending most of
    its time waiting for I/O over the network, or for a user to initiate a
    GUI action, or something external and relatively slow like that, then coroutines keep things simpler.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 04:14:05 2026
    From Newsgroup: comp.lang.c++

    On 2026-10-30, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    Threading is still definitely useful, mainly for performance, where
    the bottleneck is in CPU usage. But if a program is spending most of
    its time waiting for I/O over the network, or for a user to initiate a
    GUI action, or something external and relatively slow like that, then coroutines keep things simpler.

    I've always tried to avoid the complexities of threading; in most cases
    I can get away with round-robin scheduling. But I found that some servers
    are very slow to respond, and even when trying to do a non-blocking setup
    of a TCP/IP connection, the connect() API would unavoidably block. I had
    to spin that part off into its own thread to keep the rest of the program (including other connections) from hanging.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 05:37:23 2026
    From Newsgroup: comp.lang.c++

    On Sat, 31 Oct 2026 04:14:05 GMT, Charlie Gibbs wrote:

    I've always tried to avoid the complexities of threading; in most
    cases I can get away with round-robin scheduling. But I found that
    some servers are very slow to respond, and even when trying to do a non-blocking setup of a TCP/IP connection, the connect() API would unavoidably block. I had to spin that part off into its own thread
    to keep the rest of the program (including other connections) from
    hanging.

    HererCOs a fun little thing: if you set a socket to nonblocking and then
    do the connect(2) call, it will seemingly fail with an EINPROGRESS
    error. But in fact, the connection attempt gets initiated, and you can
    monitor its subsequent progress from your event loop.

    From the ERRORS section of <https://manpages.debian.org/connect(2)>:

    EINPROGRESS
    The socket is nonblocking and the connection cannot be
    completed immediately. (UNIX domain sockets failed with EAGAIN
    instead.) It is possible to select(2) or poll(2) for
    completion by selecting the socket for writing. After
    select(2) indicates writability, use getsockopt(2) to read the
    SO_ERROR option at level SOL_SOCKET to determine whether
    connect() completed successfully (SO_ERROR is zero) or
    unsuccessfully (SO_ERROR is one of the usual error codes
    listed here, explaining the reason for the failure).

    IrCOm not sure about doing this sort of thing from other libraries that
    wrap socket connections (e.g. SSL/TLS libraries); for these, the usual
    fallback is still available, as you say, by turning a blocking call
    into a nonblocking one by pushing it off to a separate thread.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 09:38:47 2026
    From Newsgroup: comp.lang.c++

    On Fri, 30 Oct 2026 20:37:14 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 10/30/26 17:07, boltar@caprica.universe wrote:
    On Fri, 30 Oct 2026 11:25:01 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <20261030105900.000020ce@yahoo.com>,
    Michael S <already5chosen@yahoo.com> wrote:
    Only if you intended to close the TTY the programs were started
    on. Otherwise, I don't see why it would be necessary:

    What happens when caller is GUI-style application?

    That depends on a number of factors, but basically, "it does the
    same thing". Why would it be any different?

    Windows treats GUI apps entirely differently to console ones so a Windows
    dev might not appreciate that on unix there is no demarcation - a GUI app
    simply has a network connection to the X server and it can either sit in
    an event loop waiting for events - as per a windows main thread - or go do >> other things and periodically check the X event list.


    That's where threads are useful: The GUI is one thread, and the "other >things" are in one or more other threads. There are altogether too many >programs that hang the GUI while "other things" are going on. That
    should never happen!

    If its multithreaded but that still happens someone probably has created too many critical sections with too many locks.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 19:56:10 2026
    From Newsgroup: comp.lang.c++

    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 05:37:23 -0000 (UTC)
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> gabbled:
    HererCOs a fun little thing: if you set a socket to nonblocking and
    then do the connect(2) call, it will seemingly fail with an
    EINPROGRESS error. But in fact, the connection attempt gets
    initiated, and you can monitor its subsequent progress from your
    event loop.

    Far too many devs don't know about or don't understand multiplexing
    using select() or poll(). Admittedly these are borked on Windows as
    you can't use sockets with them
    On what planet?
    which is their main raison d'etre,
    but on unix they're a very powerful tool. For simple servers with a
    low workload they can allow single threaded development simplifying
    the code immensely.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 08:32:42 2026
    From Newsgroup: comp.lang.c++

    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sat, 31 Oct 2026 05:37:23 -0000 (UTC)
    Lawrence =3D?iso-8859-13?q?D=3DFFOliveiro?=3D <ldo@nz.invalid> gabbled:
    Here=E2=80=99s a fun little thing: if you set a socket to nonblocking and >> >then do the connect(2) call, it will seemingly fail with an
    EINPROGRESS error. But in fact, the connection attempt gets
    initiated, and you can monitor its subsequent progress from your
    event loop. =20
    =20
    Far too many devs don't know about or don't understand multiplexing
    using select() or poll(). Admittedly these are borked on Windows as
    you can't use sockets with them=20

    On what planet?

    On this one where you see code that is only multithreaded in order to serve individual sockets, not because it needs to be.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 19:40:08 2026
    From Newsgroup: comp.lang.c++

    On 2026-10-31, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Sat, 31 Oct 2026 04:14:05 GMT, Charlie Gibbs wrote:

    I've always tried to avoid the complexities of threading; in most
    cases I can get away with round-robin scheduling. But I found that
    some servers are very slow to respond, and even when trying to do a
    non-blocking setup of a TCP/IP connection, the connect() API would
    unavoidably block. I had to spin that part off into its own thread
    to keep the rest of the program (including other connections) from
    hanging.

    HererCOs a fun little thing: if you set a socket to nonblocking and then
    do the connect(2) call, it will seemingly fail with an EINPROGRESS
    error. But in fact, the connection attempt gets initiated, and you can monitor its subsequent progress from your event loop.

    From the ERRORS section of <https://manpages.debian.org/connect(2)>:

    EINPROGRESS
    The socket is nonblocking and the connection cannot be
    completed immediately. (UNIX domain sockets failed with EAGAIN
    instead.) It is possible to select(2) or poll(2) for
    completion by selecting the socket for writing. After
    select(2) indicates writability, use getsockopt(2) to read the
    SO_ERROR option at level SOL_SOCKET to determine whether
    connect() completed successfully (SO_ERROR is zero) or
    unsuccessfully (SO_ERROR is one of the usual error codes
    listed here, explaining the reason for the failure).

    IrCOm not sure about doing this sort of thing from other libraries that
    wrap socket connections (e.g. SSL/TLS libraries); for these, the usual fallback is still available, as you say, by turning a blocking call
    into a nonblocking one by pushing it off to a separate thread.

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient,
    so I just spun off another thread and moved on to other things.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 21:59:41 2026
    From Newsgroup: comp.lang.c++

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sat, 31 Oct 2026 05:37:23 -0000 (UTC)
    Lawrence =3D?iso-8859-13?q?D=3DFFOliveiro?=3D <ldo@nz.invalid>
    gabbled:
    Here=E2=80=99s a fun little thing: if you set a socket to
    nonblocking and then do the connect(2) call, it will seemingly
    fail with an EINPROGRESS error. But in fact, the connection
    attempt gets initiated, and you can monitor its subsequent
    progress from your event loop. =20
    =20
    Far too many devs don't know about or don't understand multiplexing
    using select() or poll(). Admittedly these are borked on Windows as
    you can't use sockets with them=20

    On what planet?

    On this one where you see code that is only multithreaded in order to
    serve individual sockets, not because it needs to be.


    That's because many people unable to implement state machines. Or able,
    but don't like them.
    It has nothing to do with availability and functionality of select/poll
    on Windows.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Bonita Montero@Bonita.Montero@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust on Mon Nov 2 10:30:34 2026
    From Newsgroup: comp.lang.c++

    Am 14.10.2026 um 06:18 schrieb Lynn McGuire:
    rCLThe end of software secrecy is almost upon us. The death of closed source, and the final triumph of open source. rCY -Eric S. Raymond.
    -a-a https://www.battleswarmblog.com/?p=73639

    "I should have realized this a few months ago when I successfully
    decompiled the game of Firefighter from an ancient DOS shareware binary.
    My robot friend was able to tell it had been written in Borland Pascal
    from looking at the data layout; it gave me back very readable Pascal
    code with sensibly chosen function and variable names. I transpiled it
    to Rust and now ship it as part of my heritage games collection."

    Huh, so somebody has actually built a decent decompiler.-a Why do I doubt this even though ESR says otherwise?

    And he has a translator from Borland Pascal to Rust?
    I have provided Claude Code with snippets of coderCoroughly a screen's
    worth in lengthrCoon several occasions. At times, it flagged errors that weren't actually errors at all.
    It is quite possible that AI has reached a point where it can
    effectively translate small blocks of assembly code into high-level
    programming languages. However, based on my own experience with high-
    level code, I am skeptical that this would work well for larger, more
    complex applications.
    There are already AI-assisted tools for converting COBOL to Java, but
    even then, a developer must review the entire codebase afterward, as
    the conversion is never 100% accurate.
    Given this, I consider it unlikely that the process will perform any
    better in the long run.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 15:43:42 2026
    From Newsgroup: comp.lang.c++

    On Sun, 1 Nov 2026 21:59:41 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    On this one where you see code that is only multithreaded in order to
    serve individual sockets, not because it needs to be.


    That's because many people unable to implement state machines. Or able,
    but don't like them.
    It has nothing to do with availability and functionality of select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on sockets.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 16:51:47 2026
    From Newsgroup: comp.lang.c++

    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in order to
    serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or able,
    but don't like them.
    It has nothing to do with availability and functionality of select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on sockets.

    By "multiplex on sockets" do you mean supporting more then one connection
    on a single socket? Serious question here: could you tell me how this can
    be useful?

    My Win32 code does accept multiple incoming connections on the same
    port number, but each one gets its own socket. And to get back on
    thread (ahem), it uses a single thread with nonblocking sockets.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 23:46:58 2026
    From Newsgroup: comp.lang.c++

    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    On this one where you see code that is only multithreaded in order
    to serve individual sockets, not because it needs to be.


    That's because many people unable to implement state machines. Or
    able, but don't like them.
    It has nothing to do with availability and functionality of
    select/poll on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on
    sockets.


    That's nonsense. That part of Winsock2 API did not change since 1993.
    That is, in early 2000s they added poll() (WAASAPoll), but select() is
    the same BSD select() from the very beginning, just a little easier to
    use than original, because nfds is DNC.
    Now, if you woulds say that on Winsock2 select() can't multiplex
    waiting for socket I/O with waiting for other sorts of I/O (files and
    pipes) then your statement would make more sense*.
    But it does not sound like you really want to make sense. You strongly
    prefer mindless bashing.

    ----
    * - Although,
    1) of course, there (in Win32) exist not too complicated alternative
    methods to achieve such multiplexing as well. Just not via select().
    2) today, with nearly all file I/O deeply cached, multiplexing waiting
    for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing
    sockets with pipes could still make sense, infrequently.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 15:06:18 2026
    From Newsgroup: comp.lang.c++

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:
    On 2026-10-31, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Sat, 31 Oct 2026 04:14:05 GMT, Charlie Gibbs wrote:

    I've always tried to avoid the complexities of threading; in most
    cases I can get away with round-robin scheduling. But I found that
    some servers are very slow to respond, and even when trying to do a
    non-blocking setup of a TCP/IP connection, the connect() API would
    unavoidably block. I had to spin that part off into its own thread
    to keep the rest of the program (including other connections) from
    hanging.

    HererCOs a fun little thing: if you set a socket to nonblocking and then
    do the connect(2) call, it will seemingly fail with an EINPROGRESS
    error. But in fact, the connection attempt gets initiated, and you can
    monitor its subsequent progress from your event loop.

    From the ERRORS section of <https://manpages.debian.org/connect(2)>:

    EINPROGRESS
    The socket is nonblocking and the connection cannot be
    completed immediately. (UNIX domain sockets failed with EAGAIN
    instead.) It is possible to select(2) or poll(2) for
    completion by selecting the socket for writing. After
    select(2) indicates writability, use getsockopt(2) to read the
    SO_ERROR option at level SOL_SOCKET to determine whether
    connect() completed successfully (SO_ERROR is zero) or
    unsuccessfully (SO_ERROR is one of the usual error codes
    listed here, explaining the reason for the failure).

    IrCOm not sure about doing this sort of thing from other libraries that
    wrap socket connections (e.g. SSL/TLS libraries); for these, the usual
    fallback is still available, as you say, by turning a blocking call
    into a nonblocking one by pushing it off to a separate thread.

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient,
    so I just spun off another thread and moved on to other things.


    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Nov 3 02:42:44 2026
    From Newsgroup: comp.lang.c++

    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient,
    so I just spun off another thread and moved on to other things.

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 21:09:02 2026
    From Newsgroup: comp.lang.c++

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:
    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient,
    so I just spun off another thread and moved on to other things.

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.


    Well, on Linux we have aio or io_uring. The latter is more low level
    than the Windows IOCP.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 21:11:05 2026
    From Newsgroup: comp.lang.c++

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:
    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient,
    so I just spun off another thread and moved on to other things.

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.


    These are for high performance systems. But, they solve a lot of
    problems. Say your program starts to gain a lot of users?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Nov 3 07:15:06 2026
    From Newsgroup: comp.lang.c++

    On 2026-11-03, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:

    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient,
    so I just spun off another thread and moved on to other things.

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.

    These are for high performance systems. But, they solve a lot of
    problems. Say your program starts to gain a lot of users?

    In our environment that should never happen. The only legitimate
    users are those that are other elements of our software package.
    Any others (or too many seemingly legitimate users) get a rejection
    message, followed by disconnection.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Nov 3 21:51:42 2026
    From Newsgroup: comp.lang.c++

    On Mon, 2 Nov 2026 15:03:44 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote:

    On 11/2/2026 1:46 PM, Michael S wrote:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    On this one where you see code that is only multithreaded in
    order to serve individual sockets, not because it needs to be.


    That's because many people unable to implement state machines. Or
    able, but don't like them.
    It has nothing to do with availability and functionality of
    select/poll on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex
    on sockets.


    That's nonsense. That part of Winsock2 API did not change since
    1993. That is, in early 2000s they added poll() (WAASAPoll), but
    select() is the same BSD select() from the very beginning, just a
    little easier to use than original, because nfds is DNC.
    Now, if you woulds say that on Winsock2 select() can't multiplex
    waiting for socket I/O with waiting for other sorts of I/O (files
    and pipes) then your statement would make more sense*.
    But it does not sound like you really want to make sense. You
    strongly prefer mindless bashing.

    ----
    * - Although,
    1) of course, there (in Win32) exist not too complicated alternative methods to achieve such multiplexing as well. Just not via select().
    2) today, with nearly all file I/O deeply cached, multiplexing
    waiting for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing sockets with pipes could still make sense,
    infrequently.



    Have you ever used IOCP on windows?

    No, I didn't.
    IMHO, IO compleiion ports "solve" problems that do not exist today
    and mostly did not exist since 15-20 years ago.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:48:49 2026
    From Newsgroup: comp.lang.c++

    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in order to
    serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or able,
    but don't like them.
    It has nothing to do with availability and functionality of select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on sockets.


    By "multiplex on sockets" do you mean supporting more then one connection
    on a single socket? Serious question here: could you tell me how this can
    be useful?

    No I don't mean that and I can't be bother explaining what multiplexing means to someone who's clearly never used it.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:54:20 2026
    From Newsgroup: comp.lang.c++

    On Mon, 2 Nov 2026 23:46:58 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    Last time I had the misfortune to use win32 it couldn't multiplex on
    sockets.


    That's nonsense. That part of Winsock2 API did not change since 1993.
    That is, in early 2000s they added poll() (WAASAPoll), but select() is
    the same BSD select() from the very beginning, just a little easier to
    use than original, because nfds is DNC.
    Now, if you woulds say that on Winsock2 select() can't multiplex
    waiting for socket I/O with waiting for other sorts of I/O (files and
    pipes) then your statement would make more sense*.

    Yes, for some bizarre reason MS implemented the userspace sockets as some
    kind of handle instead of an integer file descriptor like every other sockets library.

    2) today, with nearly all file I/O deeply cached, multiplexing waiting
    for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing >sockets with pipes could still make sense, infrequently.

    Depends on the use case.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 11:24:54 2026
    From Newsgroup: comp.lang.c++

    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in order to >>>>> serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or able, >>>> but don't like them.
    It has nothing to do with availability and functionality of select/poll >>>> on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on sockets.


    By "multiplex on sockets" do you mean supporting more then one connection
    on a single socket? Serious question here: could you tell me how this can >> be useful?

    No I don't mean that and I can't be bother explaining what multiplexing means to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Like, search for "unix select", or something?

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:36:44 2026
    From Newsgroup: comp.lang.c++

    On 10/26/2026 10:56 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 19:51:23 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 8:39 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 16:58:04 -0700, Chris M. Thomasson wrote:

    Keeping them up to date is, afaict, manual.

    In the Linux world, we have rCLdevelopmentrCY packages versus rCLruntimerCY >>> packages.

    The development package contains the source includes, pkg-config
    info etc. The runtime version includes the actual shared library.
    So your built package has a dependency on the latter; when a user
    tries to install your package, it should automatically pull in the
    latter as necessary.

    Example from my system:

    lrwxrwxrwx 1 root root 13 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so -> libcairo.so.2
    lrwxrwxrwx 1 root root 21 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so.2 -> libcairo.so.2.11804.4
    -rw-r--r-- 1 root root 1366728 Apr 24 2026 /usr/lib/x86_64-linux-gnu/libcairo.so.2.11804.4

    Where did these come from?

    root@theon:~ # dpkg-query -S /usr/lib/x86_64-linux-gnu/libcairo.so.2 >>> libcairo2:amd64: /usr/lib/x86_64-linux-gnu/libcairo.so.2

    root@theon:~ # dpkg-query -S /usr/lib/x86_64-linux-gnu/libcairo.so
    libcairo2-dev:amd64: /usr/lib/x86_64-linux-gnu/libcairo.so

    Notice how the development library is not versioned, but is just a
    symlink to a versioned library.

    The runtime library is always versioned. This allows multiple
    versions of the library to be present at once, with some older
    packages, that havenrCOt been rebuilt, still depending on an older
    version, while up-to-date packages make use of the newer version.

    I was in the linux world for a whiel, along with solaris, etc. But
    Windows, oh my. vcpkg is a big turn.

    Windows isnrCOt even in the same league, is it.

    Windows is there. :^D
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 16:24:03 2026
    From Newsgroup: comp.lang.c++

    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in order to >>>>>> serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or able, >>>>> but don't like them.
    It has nothing to do with availability and functionality of select/poll >>>>> on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on >sockets.


    By "multiplex on sockets" do you mean supporting more then one connection >>> on a single socket? Serious question here: could you tell me how this can >>> be useful?

    No I don't mean that and I can't be bother explaining what multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is such an
    arduous task.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 23:53:55 2026
    From Newsgroup: comp.lang.c++

    On 11/4/26 17:24, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote: >>>>
    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in
    order to
    serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines. Or >>>>>> able,
    but don't like them.
    It has nothing to do with availability and functionality of
    select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on
    sockets.


    By "multiplex on sockets" do you mean supporting more then one
    connection
    on a single socket?-a Serious question here: could you tell me how
    this can
    be useful?

    No I don't mean that and I can't be bother explaining what
    multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is such an arduous task.


    That's fine too, as a hint, no issue there.

    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.

    Let's leave it at that.

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 15:38:55 2026
    From Newsgroup: comp.lang.c++

    On Wed, 4 Nov 2026 23:53:55 +0100
    Jeroen Belleman <jeroen@nospam.please> wrote:
    On 11/4/26 17:24, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe>
    wrote:
    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On this one where you see code that is only multithreaded in
    order to
    serve individual sockets, not because it needs to be.

    That's because many people unable to implement state machines.
    Or able,
    but don't like them.
    It has nothing to do with availability and functionality of
    select/poll
    on Windows.

    Last time I had the misfortune to use win32 it couldn't
    multiplex on
    sockets.


    By "multiplex on sockets" do you mean supporting more then one
    connection
    on a single socket?a Serious question here: could you tell me
    how this can
    be useful?

    No I don't mean that and I can't be bother explaining what
    multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is
    such an arduous task.


    That's fine too, as a hint, no issue there.

    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.

    Let's leave it at that.

    Jeroen Belleman
    Unless you didn't pay attention yet, boltar is asshole and proud at
    that.
    Or arshole? I'm not sure what is a correct spelling in his area.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 16:39:45 2026
    From Newsgroup: comp.lang.c++

    On Fri, 6 Nov 2026 15:38:55 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 4 Nov 2026 23:53:55 +0100
    Jeroen Belleman <jeroen@nospam.please> wrote:
    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.
    =20
    Let's leave it at that.
    =20
    Jeroen Belleman

    Unless you didn't pay attention yet, boltar is asshole and proud at
    that.
    Or arshole? I'm not sure what is a correct spelling in his area.

    Neither, but don't worry about it. When you've finished your little sucky
    thumb tantrum maybe mummy will pick up all the toys around your pram for you.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From antispam@antispam@fricas.org (Waldek Hebisch) to comp.lang.c++ on Sat Nov 7 01:17:19 2026
    From Newsgroup: comp.lang.c++

    In comp.lang.c++ Michael S <already5chosen@yahoo.com> wrote:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    On this one where you see code that is only multithreaded in order
    to serve individual sockets, not because it needs to be.


    That's because many people unable to implement state machines. Or
    able, but don't like them.
    It has nothing to do with availability and functionality of
    select/poll on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex on
    sockets.


    That's nonsense. That part of Winsock2 API did not change since 1993.
    That is, in early 2000s they added poll() (WAASAPoll), but select() is
    the same BSD select() from the very beginning, just a little easier to
    use than original, because nfds is DNC.
    Now, if you woulds say that on Winsock2 select() can't multiplex
    waiting for socket I/O with waiting for other sorts of I/O (files and
    pipes) then your statement would make more sense*.
    But it does not sound like you really want to make sense. You strongly
    prefer mindless bashing.

    ----
    * - Although,
    1) of course, there (in Win32) exist not too complicated alternative
    methods to achieve such multiplexing as well. Just not via select().
    2) today, with nearly all file I/O deeply cached, multiplexing waiting
    for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing sockets with pipes could still make sense, infrequently.

    Just curious how you solve problem of blocking in single threaded
    program? AFAIK to get data from disc one needs about 10ms or possibly
    more, which is pretty long time on modern machines. Do you assume
    that all data that you need is in RAM (or will be after short startup
    time)?
    --
    Waldek Hebisch
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 19:22:12 2026
    From Newsgroup: comp.lang.c++

    On 11/2/2026 11:15 PM, Charlie Gibbs wrote:
    On 2026-11-03, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:

    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote: >>>
    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

    I was already setting the socket to non-blocking before calling
    connect() - and yet there were times when the API blocked anyway.
    I never did figure out why, and we had a customer getting impatient, >>>>> so I just spun off another thread and moved on to other things.

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.

    These are for high performance systems. But, they solve a lot of
    problems. Say your program starts to gain a lot of users?

    In our environment that should never happen.

    then using the high performance API's is not necessary for your
    "current" use case. But, well, what happens if it does happen?


    The only legitimate
    users are those that are other elements of our software package.
    Any others (or too many seemingly legitimate users) get a rejection
    message, followed by disconnection.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.c++ on Sat Nov 7 09:41:49 2026
    From Newsgroup: comp.lang.c++

    On Sat, 7 Nov 2026 01:17:19 -0000 (UTC)
    antispam@fricas.org (Waldek Hebisch) gabbled:
    In comp.lang.c++ Michael S <already5chosen@yahoo.com> wrote:
    * - Although,
    1) of course, there (in Win32) exist not too complicated alternative
    methods to achieve such multiplexing as well. Just not via select().
    2) today, with nearly all file I/O deeply cached, multiplexing waiting
    for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing
    sockets with pipes could still make sense, infrequently.

    Just curious how you solve problem of blocking in single threaded
    program? AFAIK to get data from disc one needs about 10ms or possibly
    more, which is pretty long time on modern machines. Do you assume
    that all data that you need is in RAM (or will be after short startup
    time)?

    Both select() and poll() can be non blocking if you pass a zero timeout value to them. Any file descriptors than can be read from and/or written to will be set in the mask.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.c++ on Sat Nov 7 20:20:54 2026
    From Newsgroup: comp.lang.c++

    On Sat, 7 Nov 2026 01:17:19 -0000 (UTC)
    antispam@fricas.org (Waldek Hebisch) wrote:

    In comp.lang.c++ Michael S <already5chosen@yahoo.com> wrote:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Sun, 1 Nov 2026 21:59:41 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sun, 1 Nov 2026 08:32:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    On this one where you see code that is only multithreaded in
    order to serve individual sockets, not because it needs to be.


    That's because many people unable to implement state machines. Or
    able, but don't like them.
    It has nothing to do with availability and functionality of
    select/poll on Windows.

    Last time I had the misfortune to use win32 it couldn't multiplex
    on sockets.


    That's nonsense. That part of Winsock2 API did not change since
    1993. That is, in early 2000s they added poll() (WAASAPoll), but
    select() is the same BSD select() from the very beginning, just a
    little easier to use than original, because nfds is DNC.
    Now, if you woulds say that on Winsock2 select() can't multiplex
    waiting for socket I/O with waiting for other sorts of I/O (files
    and pipes) then your statement would make more sense*.
    But it does not sound like you really want to make sense. You
    strongly prefer mindless bashing.

    ----
    * - Although,
    1) of course, there (in Win32) exist not too complicated alternative methods to achieve such multiplexing as well. Just not via select().
    2) today, with nearly all file I/O deeply cached, multiplexing
    waiting for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing sockets with pipes could still make sense,
    infrequently.

    Just curious how you solve problem of blocking in single threaded
    program?

    I don't.
    If it is important and I expect that file operation will take
    significant time then I do it in another thread.
    May be, if I were doing server-side I'd treat it differently, but on
    cleent it's unlikely that I don't have more hardware threads than work
    to do, so separate thread is just right thing to do in such case.
    Assuming, of course, that performance at all matters, which is uncommon.


    AFAIK to get data from disc one needs about 10ms or possibly
    more, which is pretty long time on modern machines.

    I absolutly do not care about spinning rust. For close to 15 years.

    Do you assume
    that all data that you need is in RAM (or will be after short startup
    time)?


    In practice, it's extremely likely that all data is in system's file
    cache, i.e. in RAM.





    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.c++ on Sun Nov 8 09:10:38 2026
    From Newsgroup: comp.lang.c++

    On Sat, 7 Nov 2026 20:20:54 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 7 Nov 2026 01:17:19 -0000 (UTC)
    antispam@fricas.org (Waldek Hebisch) wrote:
    Just curious how you solve problem of blocking in single threaded
    program?

    I don't.
    If it is important and I expect that file operation will take
    significant time then I do it in another thread.

    So you don't understand the concept of non-blocking I/O.

    AFAIK to get data from disc one needs about 10ms or possibly
    more, which is pretty long time on modern machines.

    I absolutly do not care about spinning rust. For close to 15 years.

    15 years ago commercial SSDs were expensive, low capacity and failure prone.

    --- Synchronet 3.22a-Linux NewsLink 1.2