• =?UTF-8?Q?Re=3A_=E2=80=9CThe_end_of_software_secrecy_is_almost_upon?=

    From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 18:15:32 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 5:15 PM, boltar@caprica.universe wrote:
    On Fri, 23 Oct 2026 16:22:06 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> gabbled:
    On 10/23/2026 4:14 PM, boltar@caprica.universe wrote:
    In Windows the graphics system just starts up. On the unix X windows
    system
    initial startup requires a server IP address with optional screen
    number then
    doing a network connect. Also I don't know the win32 graphics
    subsystem but
    I suspect it differs fundamentally from the X Windows model so I have
    no idea
    how you'd square that circle unless the only API you provide is for
    top level
    GUI components as per libraries such as Gtk and Qt.

    The point I was trying to make was that in 1997, when the C++ standard
    got finalized, IUP,

    -a https://iup.sf.net/

    Had a look, requires Lua. No thanks.

    It doesn't require Lua. It comes with a Lua binding, which you can
    ignore.
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From James Kuyper@jameskuyper@alumni.caltech.edu to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 10:21:26 2026
    From Newsgroup: rec.arts.sf.written

    On 2026-10-23 05:28, David Brown wrote:
    On 22/10/2026 22:25, James Kuyper wrote:
    On 2026-10-22 12:02, Scott Lurndal wrote:
    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.
    The term in both the C and C++ standards is "abstract machine", but I
    think it was quite obvious that this is Dan meant when he wrote "virtual machine". ...

    I suspected as much, but it seemed a sufficiently odd mistake that I
    wasn't sure.
    --- 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 Fri Oct 23 09:06:00 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/26 01:01, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    In article <11bd7tj$rh4f$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>>
    Most of us have a CS degree. But then we go out into the real world, get a >>> job and find out what real programming on real products entails, not a load >>> of virtual academic naval gazing.

    That's because it's not a trade school degree. It's not there to teach
    you to program, it's there to teach you the fundamentals that you need to
    properly understand programming.

    No, it teaches you fundamentals of certain aspects of computer paradigms such as databases, graphics, AI. Most people into computers learn actual programming
    long before they hit university.

    Engineering schools are even more that way. They don't teach you much
    engineering, but they give you all the background that you need to learn
    engineering.

    Programming isn't pure engineering - its a combination of engineering, logic, art and a trade.

    If you just want a job, getting one of these degrees is not for you. It's >> not there for that.

    Bill Gates never earned a degree. He seemed to do ok.

    From what I understand, he wasn't a very good programmer, though.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 16:37:37 2026
    From Newsgroup: rec.arts.sf.written

    On 2026-10-23, Peter Flass <Peter@Iron-Spring.com> wrote:

    On 10/23/26 01:01, boltar@caprica.universe wrote:

    Bill Gates never earned a degree. He seemed to do ok.

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

    Considering how much of my career I've spent working around
    poor design decisions and outright bugs in Windows,
    I'd say that is self-evident.
    --
    /~\ 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 Cryptoengineer@petertrei@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 12:57:49 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 5:18 AM, boltar@caprica.universe wrote:
    On Fri, 23 Oct 2026 11:42:38 +0300
    Michael S <already5chosen@yahoo.com> gabbled:
    On Fri, 23 Oct 2026 08:05:13 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Thu, 22 Oct 2026 22:48:29 +0300
    Michael S <already5chosen@yahoo.com> gabbled:
    On Thu, 22 Oct 2026 14:51:31 -0000 (UTC)
    boltar@battlestar.co.uk wrote:
    I agree that the work for a CS degree is useful. If nothing else
    I understand more now.

    Most of us have a CS degree.

    I don't have it.
    How do you know about most?

    Oh I dunno, maybe 30 years in the industry working with probably
    hundreds of different programmers.


    My experience in industry beats yours by few years.
    And my statistics differ - CS graduates are not majority of computer
    programmers. At best, they are plurality.
    Regardless, the point was not industry, but audience of five particular
    newsgroups.

    Well, the majority of people in programming have some kind of STEM degree, not necessarily CS. For example if you can do electronic engineering or advance maths then programming concepts probably arn't going to be a big deal for you though I have seen plenty of code written by engineers and while it works it tends to be messy. More a case of get the job done fast so we can get on with the real work rather than create something efficient and maintainable.


    I have a degree in Biochemistry, and spent 5 year in a medical research
    lab being professionally unpleasant to rats before switch careers to
    software.

    It helped that at that time (early 80s) almost no one had a CS degree.

    My wife never finished college, but had a very successful programming
    career regardless.

    pt
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Ames@commodorejohn@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 10:32:15 2026
    From Newsgroup: rec.arts.sf.written

    On Fri, 23 Oct 2026 16:37:37 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    Bill Gates never earned a degree. He seemed to do ok.

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

    Considering how much of my career I've spent working around poor
    design decisions and outright bugs in Windows, I'd say that is
    self-evident.

    AFAIK you can't pin that one on him; the Tandy Model 100 was the last
    product he actually wrote code for, and that came out in '83, right at
    the beginning of development on Windows 1.0. Dunno that he did much on
    MS-DOS, either, as the core of that was Tim Paterson's work in, erm, "adapating" the design of CP/M to the 8086.

    --- 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 Fri Oct 23 14:01:55 2026
    From Newsgroup: rec.arts.sf.written

    In article <11bf48l$skng$1@dont-email.me>, <boltar@caprica.universe> wrote: >>If you just want a job, getting one of these degrees is not for you. It's >>not there for that.

    Bill Gates never earned a degree. He seemed to do ok.

    He is the best example I can ever give for why having an actual CS degree
    is a good idea. His lack of understanding of some basic concepts set the microcomputer industry back a decade.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 Fri Oct 23 14:09:23 2026
    From Newsgroup: rec.arts.sf.written

    John Ames <commodorejohn@gmail.com> wrote:
    AFAIK you can't pin that one on him; the Tandy Model 100 was the last
    product he actually wrote code for, and that came out in '83, right at
    the beginning of development on Windows 1.0. Dunno that he did much on >MS-DOS, either, as the core of that was Tim Paterson's work in, erm, >"adapating" the design of CP/M to the 8086.

    He continued doing code reviews well into the Win 7 era, and a lot of
    people wound up having to clean up after him. He was always very hands-on.
    I remember in 1978 him being the third tier tech support hotline for
    MBASIC bugs. He was incredibly rude.
    --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 Fri Oct 23 18:24:05 2026
    From Newsgroup: rec.arts.sf.written

    Cryptoengineer <petertrei@gmail.com> writes:
    On 10/23/2026 5:18 AM, boltar@caprica.universe wrote:
    On Fri, 23 Oct 2026 11:42:38 +0300
    Michael S <already5chosen@yahoo.com> gabbled:
    On Fri, 23 Oct 2026 08:05:13 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Thu, 22 Oct 2026 22:48:29 +0300
    Michael S <already5chosen@yahoo.com> gabbled:
    On Thu, 22 Oct 2026 14:51:31 -0000 (UTC)
    boltar@battlestar.co.uk wrote:
    I agree that the work for a CS degree is useful. If nothing else >>>>>>> I understand more now.

    Most of us have a CS degree.

    I don't have it.
    How do you know about most?

    Oh I dunno, maybe 30 years in the industry working with probably
    hundreds of different programmers.


    My experience in industry beats yours by few years.
    And my statistics differ - CS graduates are not majority of computer
    programmers. At best, they are plurality.
    Regardless, the point was not industry, but audience of five particular
    newsgroups.

    Well, the majority of people in programming have some kind of STEM degree, >> not necessarily CS. For example if you can do electronic engineering or
    advance maths then programming concepts probably arn't going to be a big deal
    for you though I have seen plenty of code written by engineers and while it >> works it tends to be messy. More a case of get the job done fast so we can >> get on with the real work rather than create something efficient and
    maintainable.


    I have a degree in Biochemistry, and spent 5 year in a medical research
    lab being professionally unpleasant to rats before switch careers to >software.

    It helped that at that time (early 80s) almost no one had a CS degree.

    I got my BSCS in 1983 (which included two years of postgrad CS
    classes[*]). Never was laid off, and got to work on very advanced
    projects for the next forty-plus years, many of which leveraged the
    postgrad coursework (mainframe OS, crypto, distributed systems, MPP systems, virtual machines, etc).

    [*] three years learning the PDP-8 and HP-3000 architectures and
    associated languages (self-taught) during High School resulted in blowing through
    the undergraduate CS requirements by the end of my sophmore year.

    The postgrad classes were particularly useful, as they were taught
    from contemporary journal articles (Lamport, Diffie-Hellman, RSA,
    Hoare (CSP), et alia).

    Most of my age-mate colleagues at Burroughs Pasadena plant in
    the 1980s also had CS or EE/CS degrees (mostly from midwestern colleges).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From John Ames@commodorejohn@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 12:02:13 2026
    From Newsgroup: rec.arts.sf.written

    On Fri, 23 Oct 2026 14:09:23 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:

    He continued doing code reviews well into the Win 7 era, and a lot of
    people wound up having to clean up after him. He was always very
    hands-on. I remember in 1978 him being the third tier tech support
    hotline for MBASIC bugs. He was incredibly rude.

    Hm, the more you know...!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn McGuire@lynnmcguire5@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 14:49:23 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 11:06 AM, Peter Flass wrote:
    On 10/23/26 01:01, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    In article <11bd7tj$rh4f$1@dont-email.me>,-a <boltar@battlestar.co.uk>
    wrote:

    Most of us have a CS degree. But then we go out into the real world,
    get a
    job and find out what real programming on real products entails, not
    a load
    of virtual academic naval gazing.

    That's because it's not a trade school degree.-a It's not there to teach >>> you to program, it's there to teach you the fundamentals that you
    need to
    properly understand programming.

    No, it teaches you fundamentals of certain aspects of computer
    paradigms such
    as databases, graphics, AI. Most people into computers learn actual
    programming
    long before they hit university.

    Engineering schools are even more that way.-a They don't teach you much
    engineering, but they give you all the background that you need to learn >>> engineering.

    Programming isn't pure engineering - its a combination of engineering,
    logic,
    art and a trade.

    If you just want a job, getting one of these degrees is not for you.
    It's
    not there for that.

    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.

    Lynn

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 12:58:24 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 1:03 AM, 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. How do you think pure software versions of virtual machines work?


    Well, a process lib needs to have certain things. Imvvho, at least
    access to robust mutex?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 13:02:44 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 1:01 AM, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    In article <11bd7tj$rh4f$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>>
    Most of us have a CS degree. But then we go out into the real world, get a >>> job and find out what real programming on real products entails, not a load >>> of virtual academic naval gazing.

    That's because it's not a trade school degree. It's not there to teach
    you to program, it's there to teach you the fundamentals that you need to
    properly understand programming.

    No, it teaches you fundamentals of certain aspects of computer paradigms such as databases, graphics, AI. Most people into computers learn actual programming
    long before they hit university.

    Agreed. Well, for me. I had LOGO, PILOT and BASIC on my first Atari when
    I was a little kiddo in the early to mid 80's. Born in 1977. I had some
    books to go with them. So, I read the damn books. Started programming!

    Now, wrt AI, well, perhaps nobody needs to buy books anymore because the
    damn thing has already "ripped them off", so to speak?


    Engineering schools are even more that way. They don't teach you much
    engineering, but they give you all the background that you need to learn
    engineering.

    Programming isn't pure engineering - its a combination of engineering, logic, art and a trade.

    If you just want a job, getting one of these degrees is not for you. It's >> not there for that.

    Bill Gates never earned a degree. He seemed to do ok.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 20:28:07 2026
    From Newsgroup: rec.arts.sf.written

    On 2026-10-23, John Ames <commodorejohn@gmail.com> wrote:

    On Fri, 23 Oct 2026 16:37:37 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> wrote:

    Bill Gates never earned a degree. He seemed to do ok.

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

    Considering how much of my career I've spent working around poor
    design decisions and outright bugs in Windows, I'd say that is
    self-evident.

    AFAIK you can't pin that one on him; the Tandy Model 100 was the last
    product he actually wrote code for, and that came out in '83, right at
    the beginning of development on Windows 1.0. Dunno that he did much on MS-DOS, either, as the core of that was Tim Paterson's work in, erm, "adapating" the design of CP/M to the 8086.

    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.
    --
    /~\ 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 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 23 20:36:52 2026
    From Newsgroup: rec.arts.sf.written

    In article <11bg7sj$l93$1@panix2.panix.com>,
    Scott Dorsey <kludge@panix.com> wrote:
    John Ames <commodorejohn@gmail.com> wrote:
    AFAIK you can't pin that one on him; the Tandy Model 100 was the last >>product he actually wrote code for, and that came out in '83, right at
    the beginning of development on Windows 1.0. Dunno that he did much on >>MS-DOS, either, as the core of that was Tim Paterson's work in, erm, >>"adapating" the design of CP/M to the 8086.

    He continued doing code reviews well into the Win 7 era, and a lot of
    people wound up having to clean up after him. He was always very hands-on.
    I remember in 1978 him being the third tier tech support hotline for
    MBASIC bugs. He was incredibly rude.

    Code reviews? For what? I can't imagine him reviewing Windows
    code; that was Dave C's baby.

    I had heard of him doing design reviews, and people I know who
    went through some of them said he was amazingly sharp, but also
    extremely critical and brooked no nonsense.

    A friend of mine did find a bug in Windows that was attributed
    to a bug he'd introduced back in MS-DOS. Wild times.

    - 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 23 20:45:27 2026
    From Newsgroup: rec.arts.sf.written

    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.

    How do you think pure software versions of virtual machines work?

    By trapping and emulating accesses to privileged state, taking
    care to ensure that the environment that the guest sees
    faithfully emulates its expectations.

    You think that's something a programming _language_ like _C_ of
    all things should standardize?

    Why?

    - 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 23 20:49:22 2026
    From Newsgroup: rec.arts.sf.written

    In article <11bfqh6$1sa3g$1@dont-email.me>,
    James Kuyper <jameskuyper@alumni.caltech.edu> wrote:
    On 2026-10-23 05:28, David Brown wrote:
    On 22/10/2026 22:25, James Kuyper wrote:
    On 2026-10-22 12:02, Scott Lurndal wrote:
    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.
    The term in both the C and C++ standards is "abstract machine", but I
    think it was quite obvious that this is Dan meant when he wrote "virtual
    machine". ...

    I suspected as much, but it seemed a sufficiently odd mistake that I
    wasn't sure.

    The danger of being overly pedantic is that one then lacks the
    ability to comprehend the difference between an abstract concept
    like a virtual machine **model** and a concrete manifestation of
    that concept, like the "abstract machine" described in the C
    standard.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 14:06:21 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 12:58 PM, Chris M. Thomasson wrote:
    On 10/23/2026 1:03 AM, 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.-a 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. How do you think pure software versions of virtual
    machines work?


    Well, a process lib needs to have certain things. Imvvho, at least
    access to robust mutex?

    Fwiw. Akin to:

    https://pubs.opengroup.org/onlinepubs/9699919799/functions/pthread_mutexattr_getrobust.html
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From William Hyde@wthyde1953@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 17:40:34 2026
    From Newsgroup: rec.arts.sf.written

    Michael S wrote:
    On Fri, 23 Oct 2026 08:05:13 -0000 (UTC)
    boltar@caprica.universe wrote:

    On Thu, 22 Oct 2026 22:48:29 +0300
    Michael S <already5chosen@yahoo.com> gabbled:
    On Thu, 22 Oct 2026 14:51:31 -0000 (UTC)
    boltar@battlestar.co.uk wrote:
    I agree that the work for a CS degree is useful. If nothing else
    I understand more now.

    Most of us have a CS degree.

    I don't have it.
    How do you know about most?

    Oh I dunno, maybe 30 years in the industry working with probably
    hundreds of different programmers.


    My experience in industry beats yours by few years.
    And my statistics differ - CS graduates are not majority of computer programmers.

    In the 70s and early 80s there was little demand for people with
    graduate degrees in physics. Most of my fellow students went on to work
    in computer science or drove taxis when their postdoctoral positions
    expired.

    I am a lousy driver and so-so programmer (at best) so I was forced to
    stick with it.

    William Hyde



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From James Kuyper@jameskuyper@alumni.caltech.edu to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 18:50:58 2026
    From Newsgroup: rec.arts.sf.written

    On 2026-10-23 17:40, William Hyde wrote:
    Michael S wrote:
    My experience in industry beats yours by few years.
    And my statistics differ - CS graduates are not majority of computer
    programmers.

    In the 70s and early 80s there was little demand for people with
    graduate degrees in physics. Most of my fellow students went on to work
    in computer science or drove taxis when their postdoctoral positions expired.

    I am a lousy driver and so-so programmer (at best) so I was forced to
    stick with it.
    I studied to be a physicist, got a BS from Caltech, and did postgraduate
    work at Cambridge. I reached that point in the 90s. I learned computer programming only with the intent of using it as a tool in support of my physics. That idea foundered on two rocks: while I am very good at understanding advanced physics, I'm not particularly good at the
    practicalities of experimental physics, and my imagination isn't good
    enough to make a good theoretical physicist. I ended up being a
    programmer who specialized in scientific programming, rather than a
    scientist who uses computer programs.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 16:56:25 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 3:50 PM, James Kuyper wrote:
    On 2026-10-23 17:40, William Hyde wrote:
    Michael S wrote:
    My experience in industry beats yours by few years.
    And my statistics differ - CS graduates are not majority of computer
    programmers.

    In the 70s and early 80s there was little demand for people with
    graduate degrees in physics. Most of my fellow students went on to work
    in computer science or drove taxis when their postdoctoral positions
    expired.

    I am a lousy driver and so-so programmer (at best) so I was forced to
    stick with it.
    I studied to be a physicist, got a BS from Caltech, and did postgraduate
    work at Cambridge. I reached that point in the 90s. I learned computer programming only with the intent of using it as a tool in support of my physics. That idea foundered on two rocks: while I am very good at understanding advanced physics, I'm not particularly good at the practicalities of experimental physics, and my imagination isn't good
    enough to make a good theoretical physicist. I ended up being a
    programmer who specialized in scientific programming, rather than a
    scientist who uses computer programs.

    Sounds good! When I got into fractals and vector fields back in
    2010'ish, I started getting really happy. It was funner than lock/wait
    free systems stuff. Here is an older work of mine from 12 years ago:

    https://youtu.be/D9XBDNVTlFE

    My vector field work is neat. It can be used for different things. It
    can use real sensor data.
    --- 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 Sat Oct 24 16:12:02 2026
    From Newsgroup: rec.arts.sf.written

    Why does Mozilla Firefox update itself just about every week?
    I use Firefox because it came installed with the Linux version I use.
    The most recent update now requires me to sign in with my Firefox
    account address ...@yahooxtra that I lost without warning over ten years
    ago when Yahoo and Xtra parted company and my address became ...@xtra.co.nz Google Chrome has over 60% of the market. Is there any reason why I
    shouldn't change to Chrome?

    Why does the Freedesktop Platform replace everything, (999 MB) every
    time Calibre is updated?
    How do I find out if this Platform services anything other than Calibre
    on my desktop?
    I can't think of any reason not to update Calibre using Calibre itself
    when it advises of updates.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn McGuire@lynnmcguire5@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust on Sat Oct 24 00:27:16 2026
    From Newsgroup: rec.arts.sf.written

    On 10/15/2026 8:35 PM, Jay Morris wrote:
    On 10/15/2026 2:13 PM, Lynn McGuire wrote:
    On 10/15/2026 10:05 AM, Scott Dorsey wrote:
    Lynn McGuire-a <lynnmcguire5@gmail.com> wrote:
    Huh, so somebody has actually built a decent decompiler.-a Why do I
    doubt
    this even though ESR says otherwise?

    Because decompiling some languages isn't that hard.-a Humans can do it
    pretty
    well, although it's harder for machines.-a It helps a lot if you have
    a symbol
    table (which it sounds like they did in the example ESR cites).

    Now... that said... I wouldn't trust anything ESR ever says and I
    would not
    hold him up as an authority.

    And he has a translator from Borland Pascal to Rust?

    That seems like a step down, doesn't it?
    --scott

    Yes on the step down to Rust.-a I wrote a lot of Turbo Pascal code back
    in the 1980s but I have to admit that I am a C++ fanboi through and
    through.-a And at my age, it will hard to change my mind on that unless
    you are writing embedded code.

    I have translated over 200,000 lines of Fortran 66/77 code to C++ this
    year so far.-a Trying to get to 300,000 lines of Fortran 66/77 code
    before the end of the year.

    Lynn

    Be sure to let us know, we'll throw a party.

    Actually, I'm close enough that that's possible.

    I would not hold my breath. This week has been slogging through the mud
    of 2,000 line Fortran 66 subroutines with hundreds of gotos.

    Lynn

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 15:22:24 2026
    From Newsgroup: rec.arts.sf.written

    On 10/24/2026 11:12 AM, Titus G wrote:
    Why does Mozilla Firefox update itself just about every week?

    There was an emergency Firefox update a few days ago, I believe, because
    of the e-something-or-other in India screwed up root key generation for
    their certificate authority. You can read the details at Ars Technica
    or elsewhere.


    https://arstechnica.com/security/2026/10/disgraced-emudhra-drops-out-of-tls-business-following-certificate-debacle/

    One of the keys was literally 4, according to the article. I wonder if
    they threw a six sided die?

    I cannot help with your Firefox account, other than say I am not using
    one yet, so there may still be a way to bypass the need. However, I
    cannot say how since I don't care about the Firefox user interface after
    they started to move everything around all the time.

    If you bring back Netscape 7 let me know.


    Best wishes, and happy browser wars!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- 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 24 08:20:22 2026
    From Newsgroup: rec.arts.sf.written

    On Fri, 23 Oct 2026 14:49:23 -0500
    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.


    --- 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 24 08:21:01 2026
    From Newsgroup: rec.arts.sf.written

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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From =?UTF-8?B?Q8OzaWzDrW4=?= =?UTF-8?B?IE5pb2Nsw6Fzw61u?= =?UTF-8?B?IEdsb3N0w6lpcg==?=@thanks-to@Taf.com to rec.arts.sf.written on Sat Oct 24 12:18:52 2026
    From Newsgroup: rec.arts.sf.written

    I ignore this newsgroup, so I am unlikely to notice a reply. I am a
    computer scientist. I do not use Firefox much, but I did install it
    onto a Microsoft-Windows-10 machine many months ago. (I do not usually
    use that computer. I do not usually use Windows 10. Whilst I use it, I
    tend to use CCleaner Browser (which a previous user probably installed
    - I never install CCleaner Browser), which is automatically loaded and
    shown on that taskbar, like Microsoft Edge.)

    Google Chrome is also installed on that computer.

    I explicitly configured that taskbar to show neither Google Chrome nor
    Firefox (unless on the rare occassions when I actually manually start
    them on that computer), but on Sunday 11th October 2026 I did manually
    start Firefox on that computer and it forcefully updated itself to
    "What's New in Firefox 157" (but right now Help --> About is saying
    Version 158.0.1 - Firefox.exe is currently timestamped Tuesday 20th
    October 2026, and Firefox.exe is in the same directory as files
    timestamped Wednesday 14th October 2026 - e.g. CoreMessagingXP.dll -
    and Sunday 11th October 2026 - e.g. updater.ini - and the next newest
    file is dated 5th September 2022 (the 1st time I saw this computer is
    1 day earlier)). Since then, Firefox insists on being on that taskbar
    just after booting and it also dares to show a window, despite no
    attempt by me to run it again after I shut this computer down on 11th
    October 2026. It says: "Update We've introduced a Firefox Terms of Use
    and updated our Privacy Notice. Please take a moment to review and
    accept. Learn more Accept". I see no obvious possibility to log on,
    but maybe logging on would be needed after reading "Terms of Use" and
    "Privacy Notice" and "Learn more" and "Accept".

    Unlike different webbrowsers, I see no absolutely easy way to see its
    browsing history's timestamps. Other than a browsing history for 11th
    October 2026, it is showing only rare usages from months ago.

    Is this market not nearly 100% had by Opera? Google Chrome and Firefox
    are gratis.
    (S. HTTP://Gloucester.Insomnia247.NL/ fuer Kontaktdaten!)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gary R. Schmidt@grschmidt@acm.org to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 01:03:05 2026
    From Newsgroup: rec.arts.sf.written

    On 24/10/2026 03:06, Peter Flass wrote:
    On 10/23/26 01:01, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    In article <11bd7tj$rh4f$1@dont-email.me>,-a <boltar@battlestar.co.uk>
    wrote:

    Most of us have a CS degree. But then we go out into the real world,
    get a
    job and find out what real programming on real products entails, not
    a load
    of virtual academic naval gazing.

    That's because it's not a trade school degree.-a It's not there to teach >>> you to program, it's there to teach you the fundamentals that you
    need to
    properly understand programming.

    No, it teaches you fundamentals of certain aspects of computer
    paradigms such
    as databases, graphics, AI. Most people into computers learn actual
    programming
    long before they hit university.

    Engineering schools are even more that way.-a They don't teach you much
    engineering, but they give you all the background that you need to learn >>> engineering.

    Programming isn't pure engineering - its a combination of engineering,
    logic,
    art and a trade.

    If you just want a job, getting one of these degrees is not for you.
    It's
    not there for that.

    Bill Gates never earned a degree. He seemed to do ok.

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

    A story I heard thirty-odd years ago about Bill Gates' purported
    programming ability:
    When MS started making money from their MSBASIC compiler, they started
    hiring real staff.
    One of them was tasked with working through the various functions that
    BASIC does, such as opening files, sorting arrays, and the like.
    When he looked at the sort routine, he exclaimed, loudly, "What idiot
    wrote this, it doesn't do anything!"
    Bill was in the room at the time, wandered over and had a look at what
    they were working on, and said, "Oh, the sort routine. I could never
    get that to work."
    Apparently it was not a career-limiting action by the programmer.

    Cheers,
    Gary B-)
    --- 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 Sat Oct 24 14:25:36 2026
    From Newsgroup: rec.arts.sf.written

    boltar@caprica.universe writes:
    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?

    It doesn't. It does have an abstraction wrapper around
    whatever threading support the target host has.
    --- 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 Sat Oct 24 07:26:04 2026
    From Newsgroup: rec.arts.sf.written

    On 10/24/26 01:21, 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...

    You can have co-operative threads. IBM CICS used to run lots of threads (tasks) concurrently, and ran them well.
    --- 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 24 14:51:36 2026
    From Newsgroup: rec.arts.sf.written

    On Sat, 24 Oct 2026 14:25:36 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:
    boltar@caprica.universe writes:
    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?

    It doesn't. It does have an abstraction wrapper around
    whatever threading support the target host has.

    And iostream is an abstraction around low level C I/O, whats your point?

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 22:55:42 2026
    From Newsgroup: rec.arts.sf.written

    On 10/24/2026 10:25 PM, Scott Lurndal wrote:
    boltar@caprica.universe writes:
    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?

    It doesn't. It does have an abstraction wrapper around
    whatever threading support the target host has.

    I don't think that's true. I currently believe, and I'm very welcoming
    of an alt.folklore.computers expert to correct me, that the Vista+
    threading model that looks extremely much like the Posix threads, only
    the names of the routines were changed, was put in place exactly to sup-
    port the C++ threading model.

    I mean, /why else/ would Microsoft bend backwards and admit their ear-
    lier Win32 threading model was flawed? And why have a subset of the Po-
    six threads and not the full thing? A side by side comparison of the
    C++ threading model might be enlightening, but I have not done this
    textbook exercise myself just yet.


    What do you think, Scott?
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- 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 Sat Oct 24 16:41:22 2026
    From Newsgroup: rec.arts.sf.written

    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.

    - Dan C.

    --- 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 Sat Oct 24 13:47:48 2026
    From Newsgroup: rec.arts.sf.written

    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 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:53:39 2026
    From Newsgroup: rec.arts.sf.written

    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
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 Sat Oct 24 13:57:02 2026
    From Newsgroup: rec.arts.sf.written

    In article <11bif5s$2pam0$1@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/24/26 01:21, 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...

    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.
    --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: rec.arts.sf.written

    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 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 Sat Oct 24 12:17:47 2026
    From Newsgroup: rec.arts.sf.written

    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.

    - Dan C.

    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?)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 13:07:38 2026
    From Newsgroup: rec.arts.sf.written

    On 10/24/2026 7:25 AM, Scott Lurndal wrote:
    boltar@caprica.universe writes:
    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?

    It doesn't. It does have an abstraction wrapper around
    whatever threading support the target host has.

    But at least they are std now since C++11? Before it was use POSIX and
    hope the compiler is compliant.

    Actually, the most import aspect, imvvho, is std::atomic.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 13:12:27 2026
    From Newsgroup: rec.arts.sf.written

    On 10/24/2026 9:41 AM, 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?

    Well, if a thread crashes, segfaults, etc it can destroy the whole
    process. But, in multi process. If a process dies, the things can be
    recovered and still run. Take a look at robust mutexes. EOWNERDEAD ?

    [...]

    --- 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 Sat Oct 24 21:24:58 2026
    From Newsgroup: rec.arts.sf.written

    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.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 21:38:43 2026
    From Newsgroup: rec.arts.sf.written

    On 2026-10-24, Scott Dorsey <kludge@panix.com> wrote:

    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.

    Exactly. Another case is a month-to-date accumulator
    at the beginning of the month.

    Still, I've heard some pretty amazing attempts to justify this
    design flaw as a feature.
    --
    /~\ 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: rec.arts.sf.written

    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 Titus G@noone@nowhere.com to rec.arts.sf.written on Sun Oct 25 11:19:05 2026
    From Newsgroup: rec.arts.sf.written

    On 24/10/2026 20:22, Johann 'Myrkraverk' Oskarsson wrote:

    Thank you for your advice which I will consider later when I have more time. --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Titus G@noone@nowhere.com to rec.arts.sf.written on Sun Oct 25 11:21:00 2026
    From Newsgroup: rec.arts.sf.written

    On 25/10/2026 01:18, C||il|!n Niocl|is|!n Glost|-ir wrote:
    I ignore this newsgroup, so I am unlikely to notice a reply.
    In case you do, I thank you for your advice which I will consider later
    when I have more 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 00:28:19 2026
    From Newsgroup: rec.arts.sf.written

    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: rec.arts.sf.written

    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 Jerry Brown@jerry@jwbrown.co.uk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 08:11:01 2026
    From Newsgroup: rec.arts.sf.written

    On Sat, 24 Oct 2026 21:38:43 GMT, Charlie Gibbs
    <cgibbs@kltpzyxm.invalid> wrote:

    On 2026-10-24, Scott Dorsey <kludge@panix.com> wrote:

    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.

    Exactly. Another case is a month-to-date accumulator
    at the beginning of the month.

    Still, I've heard some pretty amazing attempts to justify this
    design flaw as a feature.

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.
    --
    Jerry Brown

    A cat may look at a king
    (but probably won't bother)
    --- 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: rec.arts.sf.written

    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:31:00 2026
    From Newsgroup: rec.arts.sf.written

    On Sat, 24 Oct 2026 16:41:22 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    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?

    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.

    --- 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:32:33 2026
    From Newsgroup: rec.arts.sf.written

    On Sat, 24 Oct 2026 13:53:39 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    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.

    The ZX80 ran Sinclair Basic, it had nothing to do with MS and it was integer only. The ZX81 had flowing point basic and had an 8K ROM which is still
    bloody impressive.

    --- 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:34:20 2026
    From Newsgroup: rec.arts.sf.written

    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.


    --- 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:37:22 2026
    From Newsgroup: rec.arts.sf.written

    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.

    --- 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: rec.arts.sf.written

    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 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:42:47 2026
    From Newsgroup: rec.arts.sf.written

    On Sat, 24 Oct 2026 12:17:47 -0700
    Peter Flass <Peter@Iron-Spring.com> gabbled:
    On 10/24/26 09:41, Dan Cross wrote:
    In article <11bhppd$2lpkc$1@dont-email.me>, <boltar@caprica.universe> wrote:
    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.

    - Dan C.

    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.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 09:30:12 2026
    From Newsgroup: rec.arts.sf.written

    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?
    --
    This USENET posting was made without artificial intelligence,
    artificial impertinence, artificial arrogance, artificial stupidity,
    artificial flavorings or artificial colorants.
    --- 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 10:45:45 2026
    From Newsgroup: rec.arts.sf.written

    On 25/10/2026 00:11, Michael S 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.
    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.


    No one is suggesting that the threads themselves are implemented in
    pure, standard, portable C++. 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++. Suppose you have a global (i.e., external
    linkage) variable :

    int x;

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

    With threads, you are still within the same program execution - the same
    code, the same data. Thus it is appropriate that the language can
    describe the threads, and provide an execution model that can describe
    what is safe and unsafe for sharing the data. It is then highly useful
    for the programmer to have some standard data types and functions for
    doing this safe access, and wrappers around common OS functions for threads.

    With processes, you have two separate programs. Usually it is different
    code and data (with a spawn), sometimes it is the same code and a copy
    of the data (with a fork). But the programs are separate. C and C++
    model programs, not systems of programs. It is not more part of C and
    C++ than details of the filesystem.

    Of course the standard library could provide some standard wrappers for
    spawn, fork, and related process control functions. But what use would
    they be? Many of the details are OS-specific - for example, you'd
    either have to say that C++ programmers on Linux don't get "fork", or
    that C++ programmers on Windows get "fork" without realising the massive overheads involved in emulating it.

    It would be possible, of course, to have some standard library classes
    and functions here - with optional parts to make it useable on common
    OS'es. But it is very different from threading, which is integral to
    the execution model of C++ and C (since C++11 and C11) - it is that
    model that makes threading integration important. Wrappers around
    common OS calls is unlikely to give programmers anything significant.


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


    That's more realistic, and potentially more useful. And it is in
    progress. (I haven't tracked the progress for the networking TS - but
    it seems to be a lot more work than originally anticipated.)


    --- 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 Sun Oct 25 08:10:08 2026
    From Newsgroup: rec.arts.sf.written

    In article <11bker0$2pa7q$1@dont-email.me>, <boltar@caprica.universe> wrote: >On Sat, 24 Oct 2026 13:53:39 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    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.

    The ZX80 ran Sinclair Basic, it had nothing to do with MS and it was integer >only. The ZX81 had flowing point basic and had an 8K ROM which is still >bloody impressive.

    I did not realize that the ZX80 was integer only! I thought it was more
    or less like the ZX81 with everything stuffed into an asic.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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 08:37:51 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/26 02:30, Thomas Koenig wrote:
    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?


    Or some version of DOD/360? They had a couple of versions, I think. They
    kept trying to make it easier to install and maintain, but it was still DOS.

    Those times I want to run something now I use VM, because it is so much simpler.
    --- 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 08:41:47 2026
    From Newsgroup: rec.arts.sf.written

    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.
    --- 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 08:42:16 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/26 08:37, Peter Flass wrote:
    On 10/25/26 02:30, Thomas Koenig wrote:
    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?


    Or some version of DOD/360? They had a couple of versions, I think. They kept trying to make it easier to install and maintain, but it was still
    DOS.

    Those times I want to run something now I use VM, because it is so much simpler.

    DOS, sorry typo.
    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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:06:47 2026
    From Newsgroup: rec.arts.sf.written

    In article <11bl7vr$3nprb$2@dont-email.me>,
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/25/26 06:34, Dan Cross wrote:
    [snip]
    What do you think that a "thread" is?
    What do you think that a "process" is?

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

    I'm happy defer to others here, but I disagree with the premise.
    Concurrency and parallelism are useful abstractions with a rich
    history encompassing both languages and operating systems. In
    that sense they seem eminently relevant to a.f.c.

    - 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:14:18 2026
    From Newsgroup: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 13:58:43 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 8:10 AM, Scott Dorsey wrote:
    In article <11bker0$2pa7q$1@dont-email.me>, <boltar@caprica.universe> wrote:
    On Sat, 24 Oct 2026 13:53:39 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    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.

    The ZX80 ran Sinclair Basic, it had nothing to do with MS and it was integer >> only. The ZX81 had flowing point basic and had an 8K ROM which is still
    bloody impressive.

    I did not realize that the ZX80 was integer only! I thought it was more
    or less like the ZX81 with everything stuffed into an asic.
    --scott


    The Apple ][ was also integer only. The Apple ][+ had floating point.
    The top 16k of memory was ROM supporting the OS and BASIC. Relatively
    roomy compared to the ZX80/81.

    pt
    --- 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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 Chris M. Thomasson@chris.m.thomasson.1@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:19:14 2026
    From Newsgroup: rec.arts.sf.written

    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?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@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:21:27 2026
    From Newsgroup: rec.arts.sf.written

    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.



    What about separate multi threaded processes?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@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:22:34 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 1:31 AM, boltar@caprica.universe wrote:
    On Sat, 24 Oct 2026 16:41:22 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    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?

    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.
    --- 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: rec.arts.sf.written

    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 rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 14:31:49 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 9:29 AM, boltar@caprica.universe wrote:
    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.


    Make Fibers in 100% pure C++? But those are not threads. Multiple fibers
    can run on a single thread. Although, I think they can run on multiple
    threads as well. So, multiple threads, multiple fibers per thread.
    --- 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 Sun Oct 25 19:06:16 2026
    From Newsgroup: rec.arts.sf.written

    Cryptoengineer <petertrei@gmail.com> wrote:

    The Apple ][ was also integer only. The Apple ][+ had floating point.
    The top 16k of memory was ROM supporting the OS and BASIC. Relatively
    roomy compared to the ZX80/81.

    Yes, the INTBASIC was Apple code, while APPLESOFT BASIC was written by Microsoft on contract to Apple. APPLESOFT worked pretty well aside from programmable functions. It could do realtime FFTs at 0.5 samp/sec which
    was good enough for some interesting things.

    You could upgrade the roms in your original Apple ][ to the ][+ roms
    for what seemed like a fortune to me at the time but which was probably
    quite reasonable. I think you lost Sweet-16 in the process though.
    --scott

    pt
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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: rec.arts.sf.written

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 17:07:39 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 4:06 PM, Scott Dorsey wrote:
    Cryptoengineer <petertrei@gmail.com> wrote:

    The Apple ][ was also integer only. The Apple ][+ had floating point.
    The top 16k of memory was ROM supporting the OS and BASIC. Relatively
    roomy compared to the ZX80/81.

    Yes, the INTBASIC was Apple code, while APPLESOFT BASIC was written by Microsoft on contract to Apple. APPLESOFT worked pretty well aside from programmable functions. It could do realtime FFTs at 0.5 samp/sec which
    was good enough for some interesting things.

    You could upgrade the roms in your original Apple ][ to the ][+ roms
    for what seemed like a fortune to me at the time but which was probably
    quite reasonable. I think you lost Sweet-16 in the process though.
    --scott

    pt



    IIGS with some extra memory, and a HD, beat a Mac back in the say, iirc,
    Mac SE. The Mac iicx, or iise, well they were pretty fun.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Rich Alderson@news@alderson.users.panix.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 20:10:26 2026
    From Newsgroup: rec.arts.sf.written

    Lynn McGuire <lynnmcguire5@gmail.com> writes:

    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.

    The original Altair BASIC is only an interpreter; there is no compiler available.

    The interpreter requires 4K minimum to run.

    The interpreter is assembled from source on a PDP-10 with at least 128K (and preferably more) of 36 bit words,because it's implemented as local system call macros in PDP-10 assembler.

    Bill wrote the basic framework, Monte Davidoff wrote the transcendental math functions, and Paul Allen wrote the PDP-10 code to do the assembly.

    NB: I worked for Paul building Living Computers: Museum+Labs and working there as an engineer from 2003-2018, then till 2020 when we closed due to the pandemic.
    I've seen the original code, with named attributions.
    --
    Rich Alderson news@alderson.users.panix.com
    Audendum est, et veritas investiganda; quam etiamsi non assequamur,
    omnino tamen proprius, quam nunc sumus, ad eam perveniemus.
    --Galen --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 17:22:28 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 1:56 PM, Michael S wrote:
    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.







    I tried to do a little something, no atomics, but, since I am able to
    access comp.lang.c++ agai, lets see if I can find it:

    https://groups.google.com/g/comp.lang.c/c/WPH7ed5uS4Y/m/ohiP-hUWkcAJ

    Content:
    ___________________________________



    ________________________________________________________________
    #if ! defined (CT_C11_THREADS_H_EMULATION_H)
    # define CT_C11_THREADS_H_EMULATION_H 1
    # if defined (__cplusplus)
    extern "C"
    {
    # endif



    #if defined (CT_C11_THREADS_H_PRINTF_LOG)
    # include <stdio.h>
    # define CT_C11_THREADS_H_PRINTF(mp_exp) printf mp_exp
    #else
    # define CT_C11_THREADS_H_PRINTF(mp_exp) ((void)(0))
    #endif




    #include <stdlib.h>
    #include <pthread.h>
    #include <assert.h>


    typedef int (*ct_thrd_start_t) (void*);

    struct ct_thrd_user
    {
    pthread_t ptid;
    };


    struct ct_thrd_sys
    {
    ct_thrd_start_t fp_user;
    void* user_ctx;
    int user_ret;
    };


    enum ct_thrd_sys_status
    {
    ct_thrd_success = 0,
    ct_thrd_nomem = 1,
    ct_thrd_timedout = 2,
    ct_thrd_busy = 3,
    ct_thrd_error = 4
    };





    /* low-level system threading API's __________________________________________________________________*/
    static struct ct_thrd_sys*
    ct_thrd_sys_create(
    ct_thrd_start_t fp_user,
    void* user_ctx
    );

    static void
    ct_thrd_sys_destroy(
    struct ct_thrd_sys* const self
    );

    static void*
    ct_thrd_sys_entry(
    void* self_raw
    );



    struct ct_thrd_sys*
    ct_thrd_sys_create(
    ct_thrd_start_t fp_user,
    void* user_ctx
    ){
    struct ct_thrd_sys* const self = malloc(sizeof(*self));

    if (self)
    {
    self->fp_user = fp_user;
    self->user_ctx = user_ctx;
    self->user_ret = 0;
    }

    CT_C11_THREADS_H_PRINTF(("ct_thrd_sys_create = %p\r\n", (void*)self));

    return self;
    }

    void
    ct_thrd_sys_destroy(
    struct ct_thrd_sys* const self
    ){
    free(self);

    CT_C11_THREADS_H_PRINTF(
    ("ct_thrd_sys_destroy(self = %p)\r\n", (void*)self)
    );
    }


    void*
    ct_thrd_sys_entry(
    void* self_raw
    ){
    struct ct_thrd_sys* const self = self_raw;

    CT_C11_THREADS_H_PRINTF(
    ("ct_thrd_sys_entry(self_raw = %p):Enter\r\n", self_raw)
    );

    self->user_ret = self->fp_user(self->user_ctx);

    CT_C11_THREADS_H_PRINTF(
    ("ct_thrd_sys_entry(self_raw = %p):Exit = %p\r\n", self_raw,
    (void*)self)
    );

    return self;
    }






    /* C11 emulation API layer __________________________________________________________________*/


    /* Threading API ______________________________________________________________*/
    typedef struct ct_thrd_user ct_thrd_t;


    static int
    ct_thrd_create(
    ct_thrd_t* uself,
    ct_thrd_start_t fp_user,
    void* user_ctx
    );

    static int
    ct_thrd_join(
    ct_thrd_t self,
    int* user_retv
    );


    int
    ct_thrd_create(
    ct_thrd_t* uself,
    ct_thrd_start_t fp_user,
    void* user_ctx
    ){
    struct ct_thrd_sys* const self =
    ct_thrd_sys_create(fp_user, user_ctx);

    if (self)
    {
    int status = pthread_create(&uself->ptid, NULL, ct_thrd_sys_entry,
    self);

    if (! status)
    {
    return ct_thrd_success;
    }

    ct_thrd_sys_destroy(self);
    }

    return ct_thrd_nomem;
    }


    int
    ct_thrd_join(
    ct_thrd_t self,
    int* user_retv
    ){
    void* ptjret = NULL;

    pthread_join(self.ptid, &ptjret);

    if (ptjret)
    {
    struct ct_thrd_sys* const self = ptjret;

    if (user_retv)
    {
    *user_retv = self->user_ret;
    }

    ct_thrd_sys_destroy(self);

    return ct_thrd_success;
    }

    return ct_thrd_error;
    }




    /* Thread Specific Storage API ______________________________________________________________*/
    typedef pthread_key_t ct_tss_t;
    typedef void(*ct_tss_dtor_t) (void*);

    static int
    ct_tss_create(
    ct_tss_t* self,
    ct_tss_dtor_t fp_user_dtor
    );

    static void
    ct_tss_delete(
    ct_tss_t self
    );

    static int
    ct_tss_set(
    ct_tss_t self,
    void* user_ctx
    );

    #define ct_tss_get(mp_self) pthread_getspecific((mp_self))



    int
    ct_tss_create(
    ct_tss_t* self,
    ct_tss_dtor_t fp_user_dtor
    ){
    int status = pthread_key_create(self, fp_user_dtor);

    if (!status)
    {
    return ct_thrd_success;
    }

    return ct_thrd_error;
    }


    void
    ct_tss_delete(
    ct_tss_t self
    ){
    int status = pthread_key_delete(self);

    if (! status)
    {
    return;
    }

    assert(! status);
    }


    int
    ct_tss_set(
    ct_tss_t self,
    void* user_ctx
    ){
    int status = pthread_setspecific(self, user_ctx);

    if (!status)
    {
    return ct_thrd_success;
    }

    return ct_thrd_error;
    }




    /* Mutex API
    ______________________________________________________________*/
    typedef pthread_mutex_t ct_mtx_t;

    enum {
    ct_mtx_plain = 1,
    ct_mtx_recursive = 2,
    ct_mtx_timed = 4
    };


    int
    ct_mtx_init(
    ct_mtx_t* self,
    int type
    ){
    if (type == ct_mtx_plain)
    {
    int status = pthread_mutex_init(self, NULL);

    if (! status)
    {
    return ct_thrd_success;
    }
    }

    return ct_thrd_error;
    }


    void
    ct_mtx_destroy(
    ct_mtx_t* self
    ){
    int status = pthread_mutex_destroy(self);

    if (! status)
    {
    return;
    }

    assert(! status);
    }


    int
    ct_mtx_lock(
    ct_mtx_t* self
    ){
    int status = pthread_mutex_lock(self);

    if (! status)
    {
    return ct_thrd_success;
    }

    assert(! status);

    return ct_thrd_error;
    }


    int
    ct_mtx_unlock(
    ct_mtx_t* self
    ){
    int status = pthread_mutex_unlock(self);

    if (!status)
    {
    return ct_thrd_success;
    }

    assert(! status);

    return ct_thrd_error;
    }




    /* Mutex API
    ______________________________________________________________*/
    typedef pthread_cond_t ct_cnd_t;

    int
    ct_cnd_init(
    ct_cnd_t* self
    ){
    int status = pthread_cond_init(self, NULL);

    if (! status)
    {
    return ct_thrd_success;
    }

    return ct_thrd_error;
    }


    void
    ct_cnd_destroy(
    ct_cnd_t* self
    ){
    int status = pthread_cond_destroy(self);

    if (! status)
    {
    return;
    }

    assert(! status);
    }


    int
    ct_cnd_signal(
    ct_cnd_t* self
    ){
    int status = pthread_cond_signal(self);

    if (! status)
    {
    return ct_thrd_success;
    }

    assert(! status);

    return ct_thrd_error;
    }


    int
    ct_cnd_broadcast(
    ct_cnd_t* self
    ){
    int status = pthread_cond_broadcast(self);

    if (! status)
    {
    return ct_thrd_success;
    }

    assert(! status);

    return ct_thrd_error;
    }


    int
    ct_cnd_wait(
    ct_cnd_t* self,
    ct_mtx_t* mtx
    ){
    int status = pthread_cond_wait(self, mtx);

    if (! status)
    {
    return ct_thrd_success;
    }

    assert(! status);

    return ct_thrd_error;
    }






    /* Mock up the final C11 API with some macros... ;^o ______________________________________________________________*/



    /* C11 threading API
    _________________________________________________*/
    #define thrd_success ct_thrd_success
    #define thrd_nomem ct_thrd_nomem
    #define thrd_timedout ct_thrd_timedout
    #define thrd_busy ct_thrd_busy
    #define thrd_error ct_thrd_error

    #define thrd_t ct_thrd_t

    #define thrd_create ct_thrd_create
    #define thrd_join ct_thrd_join



    /* C11 thread specific storage API _________________________________________________*/
    #define tss_t ct_tss_t

    #define tss_create ct_tss_create
    #define tss_delete ct_tss_delete
    #define tss_set ct_tss_set
    #define tss_get ct_tss_get



    /* C11 mutex API
    _________________________________________________*/
    #define mtx_plain ct_mtx_plain
    #define mtx_recursive ct_mtx_recursive
    #define mtx_timed ct_mtx_timed

    #define mtx_t ct_mtx_t

    #define mtx_init ct_mtx_init
    #define mtx_destroy ct_mtx_destroy
    #define mtx_lock ct_mtx_lock
    #define mtx_unlock ct_mtx_unlock



    /* C11 condition variable API _________________________________________________*/
    #define cnd_t ct_cnd_t

    #define cnd_init ct_cnd_init
    #define cnd_destroy ct_cnd_destroy
    #define cnd_signal ct_cnd_signal
    #define cnd_broadcast ct_cnd_broadcast
    #define cnd_wait ct_cnd_wait




    # if defined (__cplusplus)
    }
    # endif
    #endif
    ________________________________________________________________



    This is in my personal coding style. I am sorry if it ends up pissing you
    off!

    ;^o




    Anyway, what do you think?

    :^)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:01:39 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 1:37 AM, 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.


    So does C11.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:03:01 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 1:42 AM, boltar@caprica.universe wrote:
    On Sat, 24 Oct 2026 12:17:47 -0700
    Peter Flass <Peter@Iron-Spring.com> gabbled:
    On 10/24/26 09:41, Dan Cross wrote:
    In article <11bhppd$2lpkc$1@dont-email.me>,
    <boltar@caprica.universe> wrote:
    What, pray tell, do you think that a _thread_ is?-a And how is it
    different from a _process_?-a For that matter, what do you think
    that a _process_ is?

    Please, take all the time you need to answer.

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

    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.


    Have you ever tried to sync up multiple processes each running multiple threads? When is the last time you used a robust mutex?
    --- 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 22:54:14 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 7:06 PM, Scott Dorsey wrote:
    Cryptoengineer <petertrei@gmail.com> wrote:

    The Apple ][ was also integer only. The Apple ][+ had floating point.
    The top 16k of memory was ROM supporting the OS and BASIC. Relatively
    roomy compared to the ZX80/81.

    Yes, the INTBASIC was Apple code, while APPLESOFT BASIC was written by Microsoft on contract to Apple. APPLESOFT worked pretty well aside from programmable functions. It could do realtime FFTs at 0.5 samp/sec which
    was good enough for some interesting things.

    You could upgrade the roms in your original Apple ][ to the ][+ roms
    for what seemed like a fortune to me at the time but which was probably
    quite reasonable. I think you lost Sweet-16 in the process though.
    --scott

    pt

    I distinctly recall working with Sweet-16 on my ][+ back in the day,
    but can't recall the details.

    pt
    --- 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: rec.arts.sf.written

    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 Jerry Brown@jerry@jwbrown.co.uk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 07:59:39 2026
    From Newsgroup: rec.arts.sf.written

    On Sun, 25 Oct 2026 09:30:12 -0000 (UTC), Thomas Koenig
    <tkoenig@netcologne.de> wrote:

    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?

    That's ringing a vague bell.

    My time on the 9370 was short compared to the 3090, so all I can
    remember were things like the file handling was MUCH simpler (no need
    specify record types and block sizes and the foreground scripting
    language REXX was much nicer than the CLIST we used on the mainframe -
    it had stacks for storing and processing data, which was fun.

    The only command I can remember was when I had my operator hat on and
    a user wanted to access the 3422 tape drive I had to ATTACH the
    physical 3 digit id of the tape drive to the logical 3 digit id they
    were using (in retrospect I see this was its equivalent of unix mount
    command).
    --
    Jerry Brown

    A cat may look at a king
    (but probably won't bother)
    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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 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 10:01:55 2026
    From Newsgroup: rec.arts.sf.written

    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.

    --- 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 10:02:41 2026
    From Newsgroup: rec.arts.sf.written

    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?

    --- 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 10:33:22 2026
    From Newsgroup: rec.arts.sf.written

    In article <5e1udl9hs8733aqpjenq0vk71v3pn25q8n@jwbrown.co.uk>,
    Jerry Brown <jerry@jwbrown.co.uk.invalid> wrote:
    On Sun, 25 Oct 2026 09:30:12 -0000 (UTC), Thomas Koenig ><tkoenig@netcologne.de> wrote:

    Jerry Brown <jerry@jwbrown.co.uk.invalid> schrieb:

    I supported an IBM 9370 back in the 90s and whatever operating system
    it ran (completely different to the 3090 mainframe with JCL, etc it
    was supposed to replace) didn't allow zero length files.

    VM/CMS?

    That's ringing a vague bell.

    My time on the 9370 was short compared to the 3090, so all I can
    remember were things like the file handling was MUCH simpler (no need
    specify record types and block sizes and the foreground scripting
    language REXX was much nicer than the CLIST we used on the mainframe -
    it had stacks for storing and processing data, which was fun.

    The only command I can remember was when I had my operator hat on and
    a user wanted to access the 3422 tape drive I had to ATTACH the
    physical 3 digit id of the tape drive to the logical 3 digit id they
    were using (in retrospect I see this was its equivalent of unix mount >command).

    That sounds like VM/ESA, all right. Command list `LIST` and
    `TYPE` and a three-field file name relative to a "minidisk"?
    REXX was the "usual" scripting language.

    VM was kind of neat.

    - Dan C.

    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 Titus G@noone@nowhere.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 08:43:19 2026
    From Newsgroup: rec.arts.sf.written

    On 27/10/2026 08:10, Blaine wrote:

    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.

    What a laugh. You are the clown replying to Starmaker.


    --- 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: rec.arts.sf.written

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:03:25 2026
    From Newsgroup: rec.arts.sf.written

    On 10/26/2026 3:01 AM, 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-a <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.-a 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.

    Afaict, its not useless.

    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.
    --- 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: rec.arts.sf.written

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:05:30 2026
    From Newsgroup: rec.arts.sf.written

    On 10/26/2026 2:59 AM, boltar@caprica.universe wrote:
    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.


    3 level locking? What do you mean?
    --- 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: rec.arts.sf.written

    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 rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:12:24 2026
    From Newsgroup: rec.arts.sf.written

    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.

    (google groups wrt usenet seems to be back up now) https://groups.google.com/g/comp.lang.c++/c/sV4WC_cBb9Q/m/SkSqpSxGCAAJ

    some of my old relacy code:

    #include <relacy/relacy.hpp>
    #include <cstdio>
    #include <cstddef>
    #include <cstdlib>
    #include <string>
    #include <vector>

    #if ! defined (NDEBUG)
    # define CT_DBG_PRINTF(e) std::printf e
    #else
    # define CT_DBG_PRINTF(e) ((void)0)
    #endif


    #define CT_THREADS (5)
    #define CT_MUTEX_TABLE_N (64)


    struct ct_mutex_table
    {
    rl::mutex m_mutexs[CT_MUTEX_TABLE_N];

    std::size_t
    hash_ptr(
    void* p
    ) const {
    return rl::hash_ptr(p, CT_MUTEX_TABLE_N);
    }
    };


    struct ct_thread_mutex_hash
    {
    std::vector<std::size_t> m_hashed_idxs;

    // must be before any locks!
    void finalize()
    {
    std::sort(
    m_hashed_idxs.begin(),
    m_hashed_idxs.end());

    m_hashed_idxs.erase(
    std::unique(
    m_hashed_idxs.begin(),
    m_hashed_idxs.end()),
    m_hashed_idxs.end());
    }


    // BEFORE WE CALL, WE NEED TO sort and dedup before this.
    void
    lock(
    ct_mutex_table& mutex_table
    ) {
    for (auto& mtx_idx : m_hashed_idxs)
    {
    rl::mutex& mtx = mutex_table.m_mutexs[mtx_idx];
    mtx.lock($);
    }
    }

    // does not really even need to be reversed...
    void
    unlock(
    ct_mutex_table& mutex_table
    ) {
    for (auto& mtx_idx : m_hashed_idxs)
    {
    rl::mutex& mtx = mutex_table.m_mutexs[mtx_idx];
    mtx.unlock($);
    }
    }
    };


    struct ct_state
    {
    ct_mutex_table m_mutex_table;
    VAR_T(int) m_var_0 = 0;
    VAR_T(int) m_var_1 = 1;
    VAR_T(int) m_var_2 = 2;


    void worker_thread_a()
    {
    ct_thread_mutex_hash self_hash;

    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_0));

    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_1));

    self_hash.finalize();

    self_hash.lock(m_mutex_table);

    VAR(m_var_0) = 42;
    VAR(m_var_1) = 128;

    self_hash.unlock(m_mutex_table);
    }

    void worker_thread_b()
    {
    ct_thread_mutex_hash self_hash;

    // Seed!
    {
    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_1));

    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_0));
    }


    // Okay... Finalize it...
    {
    self_hash.finalize();
    }


    // Finally, we can lock the bastard!
    {
    self_hash.lock(m_mutex_table);

    {
    VAR(m_var_0) = 99;
    VAR(m_var_1) = 77;
    }

    self_hash.unlock(m_mutex_table);
    }
    }
    };


    struct ct_multex_relacy_test_v000
    : rl::test_suite<ct_multex_relacy_test_v000, CT_THREADS>
    {
    ct_state m_state = { };

    void before()
    {
    // not sure to init m_state here. Is it already init?
    }

    void
    thread(
    unsigned tidx
    ) {
    if (tidx == 0)
    m_state.worker_thread_a();
    else
    m_state.worker_thread_b();
    }
    };


    int main(int argc, char** argv)
    {
    {
    rl::test_params p;

    p.iteration_count = argc > 1 ? (unsigned)atoi(argv[1]) : 100000;
    p.execution_depth_limit = 100000;

    if (argc > 2) {
    std::string m = argv[2];
    if (m == "full") p.search_type = rl::sched_full;
    else if (m == "bound") { p.search_type = rl::sched_bound; p.context_bound = argc > 3 ? atoi(argv[3]) : 2; }
    }

    rl::simulate<ct_multex_relacy_test_v000>(p);
    }

    return 0;
    }


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:20:39 2026
    From Newsgroup: rec.arts.sf.written

    On 10/26/2026 3:02 AM, 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?


    My point is that you seem to be daft on these issues. Are you trolling?
    --- 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: rec.arts.sf.written

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:44:09 2026
    From Newsgroup: rec.arts.sf.written

    On 10/26/2026 1:40 PM, Michael S wrote:
    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.

    Ahhh! I call that a read/write mutex. Okay.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn McGuire@lynnmcguire5@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 17:08:58 2026
    From Newsgroup: rec.arts.sf.written

    On 10/23/2026 11:06 AM, Peter Flass wrote:
    On 10/23/26 01:01, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 12:19:49 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) gabbled:
    In article <11bd7tj$rh4f$1@dont-email.me>,-a <boltar@battlestar.co.uk>
    wrote:

    Most of us have a CS degree. But then we go out into the real world,
    get a
    job and find out what real programming on real products entails, not
    a load
    of virtual academic naval gazing.

    That's because it's not a trade school degree.-a It's not there to teach >>> you to program, it's there to teach you the fundamentals that you
    need to
    properly understand programming.

    No, it teaches you fundamentals of certain aspects of computer
    paradigms such
    as databases, graphics, AI. Most people into computers learn actual
    programming
    long before they hit university.

    Engineering schools are even more that way.-a They don't teach you much
    engineering, but they give you all the background that you need to learn >>> engineering.

    Programming isn't pure engineering - its a combination of engineering,
    logic,
    art and a trade.

    If you just want a job, getting one of these degrees is not for you.
    It's
    not there for that.

    Bill Gates never earned a degree. He seemed to do ok.

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

    https://www.joelonsoftware.com/2006/06/16/my-first-billg-review/

    "Then I sat down to write the Excel Basic spec, a huge document that
    grew to hundreds of pages. I think it was 500 pages by the time it was
    done. (rCLWaterfall,rCY you snicker; yeah yeah shut up.)"

    "In my BillG review meeting, the whole reporting hierarchy was there,
    along with their cousins, sisters, and aunts, and a person who came
    along from my team whose whole job during the meeting was to keep an
    accurate count of how many times Bill said the F word. The lower the f***-count, the better."

    "rCa and THERE WERE NOTES IN ALL THE MARGINS. ON EVERY PAGE OF THE SPEC.
    HE HAD READ THE WHOLE GODDAMNED THING AND WRITTEN NOTES IN THE MARGINS."

    He Read The Whole Thing! [OMG SQUEEE!]

    I turned down an unsolicited job at Microsoft in 1987. In retrospect,
    it may have been a bad decision. Then again, BillG seems to be a crazy overseer from the latest reports.

    Lynn

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

    On 10/25/2026 8:56 AM, Scott Lurndal wrote:
    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.

    POSIC, bow down, even way before C11. It still can be used, and is very
    nice.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 20:16:52 2026
    From Newsgroup: rec.arts.sf.written

    On 10/26/2026 1:09 PM, Michael S wrote:
    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.
    Seems so! Damn it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 20:44:49 2026
    From Newsgroup: rec.arts.sf.written

    On 10/25/2026 2:45 AM, David Brown wrote:
    On 25/10/2026 00:11, Michael S 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-a <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.-a 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.-a 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?-a And how is it
    different from a _process_?-a 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.

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


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

    -a-a-a-aint 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.
    --- 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 Tue Oct 27 09:06:26 2026
    From Newsgroup: rec.arts.sf.written

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

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

    --- 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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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:01:15 2026
    From Newsgroup: rec.arts.sf.written

    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.

    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 14:04:02 2026
    From Newsgroup: rec.arts.sf.written

    On 10/28/2026 2:01 AM, 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.


    On Windows? Get used to

    https://learn.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-wsaduplicatesocketa

    DuplicateHandle

    etc...

    You can have multiple multi threaded processes on windows. Even ones
    with multiple fibers running on the multiple threads per process.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 14:05:34 2026
    From Newsgroup: rec.arts.sf.written

    On 10/28/2026 1:58 AM, 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.

    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.


    Its simple, if you don't like windows, do use the damn pile.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 14:06:09 2026
    From Newsgroup: rec.arts.sf.written

    On 10/28/2026 2:05 PM, Chris M. Thomasson wrote:
    On 10/28/2026 1:58 AM, 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?-a-a "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-a - 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.


    Its simple, if you don't like windows, do use the damn pile.

    Argh! Damn typos! Don't use the damn pile! :^)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 14:09:32 2026
    From Newsgroup: rec.arts.sf.written

    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.
    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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:19:01 2026
    From Newsgroup: rec.arts.sf.written

    On Wed, 28 Oct 2026 14:04:02 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/28/2026 2:01 AM, 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.


    On Windows? Get used to

    https://learn.microsoft.com/en-us/windows/win32/api/winsock2/nf-winsock2-wsadup
    licatesocketa

    DuplicateHandle

    Right, lets duplicate everything manually - so much easier than one system call.
    And thats just file descriptors.

    --- 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:20:39 2026
    From Newsgroup: rec.arts.sf.written

    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.

    --- 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: rec.arts.sf.written

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 12:49:55 2026
    From Newsgroup: rec.arts.sf.written

    On 10/29/2026 9:19 AM, boltar@caprica.universe wrote:
    On Wed, 28 Oct 2026 14:04:02 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/28/2026 2:01 AM, 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.


    On Windows? Get used to

    https://learn.microsoft.com/en-us/windows/win32/api/winsock2/nf-
    winsock2-wsadup
    licatesocketa

    DuplicateHandle

    Right, lets duplicate everything manually - so much easier than one
    system call.
    And thats just file descriptors.


    Do we actually need everything, or just a subset?
    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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 Thu Oct 29 15:13:58 2026
    From Newsgroup: rec.arts.sf.written

    On 10/29/26 13:39, Michael S wrote:
    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.

    Just an old idea from OS/360 MVT circa 1965-66. OS calls them tasks.
    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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 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:21:03 2026
    From Newsgroup: rec.arts.sf.written

    On Thu, 29 Oct 2026 12:49:55 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/29/2026 9:19 AM, boltar@caprica.universe wrote:
    Right, lets duplicate everything manually - so much easier than one
    system call.
    And thats just file descriptors.


    Do we actually need everything, or just a subset?

    That will depend entirely on the application. There could be a boatload of startup config in memory plus all the enviroment variables.

    --- 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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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: rec.arts.sf.written

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 30 11:05:53 2026
    From Newsgroup: rec.arts.sf.written

    On 10/30/2026 4:25 AM, boltar@caprica.universe wrote:
    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.


    Multi process with shared memory can be tricky indeed. Step one, you
    need to ponder on making it "robust". Threads do not need to be robust.
    Well, you should not have a thread up and die anyway. Now, for multi
    process, that should be handled. There are many different ways.
    --- 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: rec.arts.sf.written

    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 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: rec.arts.sf.written

    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 Nuno Silva@nunojsilva@invalid.invalid to rec.arts.sf.written,alt.folklore.computers on Sat Oct 31 11:40:54 2026
    From Newsgroup: rec.arts.sf.written

    [ I'm removing the comp.lang.* groups from this reply. ]

    On 2026-10-24, Johann 'Myrkraverk' Oskarsson wrote:

    On 10/24/2026 11:12 AM, Titus G wrote:
    Why does Mozilla Firefox update itself just about every week?

    There was an emergency Firefox update a few days ago, I believe, because
    of the e-something-or-other in India screwed up root key generation for
    their certificate authority. You can read the details at Ars Technica
    or elsewhere.

    https://arstechnica.com/security/2026/10/disgraced-emudhra-drops-out-of-tls-business-following-certificate-debacle/

    One of the keys was literally 4, according to the article. I wonder if
    they threw a six sided die?

    Several keys were found to be under 256, not 256 bits, the number
    256. Just 8 bits, tops. (Ok, I see the article already mentions this!)

    Somebody made a neat plot of the private keys:

    <https://files.cloudisland.nz/media_attachments/files/117/476/240/597/299/609/original/93a9704c02f45104.png>

    From: <https://cloudisland.nz/@yaakov/117476242408958038>

    I cannot help with your Firefox account, other than say I am not using
    one yet, so there may still be a way to bypass the need. However, I
    cannot say how since I don't care about the Firefox user interface after
    they started to move everything around all the time.

    If you bring back Netscape 7 let me know.

    Did it ever go away? :-)


    (New SeaMonkey release including a built-in certificate store update
    should be coming soon, <news://news.blueworldhosting.com/nka82hFeaemU1@mid.individual.net>)

    Best wishes, and happy browser wars!
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 13:11:29 2026
    From Newsgroup: rec.arts.sf.written

    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    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-a <already5chosen@yahoo.com> wrote:
    Only if you intended to close the TTY the programs were started
    on.-a 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".-a 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.


    What do you mean? Is the GUI deadlocking?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 13:14:47 2026
    From Newsgroup: rec.arts.sf.written

    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    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-a <already5chosen@yahoo.com> wrote:
    Only if you intended to close the TTY the programs were started
    on.-a 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".-a 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.


    Makes no sense at all. Have you taken a look at my multex? It can create
    a shit lod of mutexes, and never deadlock. It keeps a strict locking
    order. Sorts and dedups the mutexes. Also, notice that an object does
    not need its own mutex:





    So, I have the most recent version and coded up my old multex algo. It
    100% dead lock free and allows a thread to locks multiple objects in any
    order and lock them. All of the lock ordering is taken care of in the
    finalize function. Basically a thread seeds its per thread lock indices
    with addresses to objects it wants to lock. Calls finalize, then locks
    them. Does its thing and then unlocks them. Fwiw, here is my Relacy test output:

    struct ct_multex_relacy_test_v000
    65% (65536/100000)
    iterations: 100000
    total time: 9390
    throughput: 10649


    D:\ct_dev\ct_msvc\projects\ct_relacy_test\x64\Debug\ct_relacy_test.exe (process 13356) exited with code 0 (0x0).
    Press any key to close this window . . .


    Any my code:

    #include <relacy/relacy.hpp>
    #include <cstdio>
    #include <cstddef>
    #include <cstdlib>
    #include <string>
    #include <vector>

    #if ! defined (NDEBUG)
    # define CT_DBG_PRINTF(e) std::printf e
    #else
    # define CT_DBG_PRINTF(e) ((void)0)
    #endif


    #define CT_THREADS (5)
    #define CT_MUTEX_TABLE_N (64)


    struct ct_mutex_table
    {
    rl::mutex m_mutexs[CT_MUTEX_TABLE_N];

    std::size_t
    hash_ptr(
    void* p
    ) const {
    return rl::hash_ptr(p, CT_MUTEX_TABLE_N);
    }
    };


    struct ct_thread_mutex_hash
    {
    std::vector<std::size_t> m_hashed_idxs;

    // must be before any locks!
    void finalize()
    {
    std::sort(
    m_hashed_idxs.begin(),
    m_hashed_idxs.end());

    m_hashed_idxs.erase(
    std::unique(
    m_hashed_idxs.begin(),
    m_hashed_idxs.end()),
    m_hashed_idxs.end());
    }


    // BEFORE WE CALL, WE NEED TO sort and dedup before this.
    void
    lock(
    ct_mutex_table& mutex_table
    ) {
    for (auto& mtx_idx : m_hashed_idxs)
    {
    rl::mutex& mtx = mutex_table.m_mutexs[mtx_idx];
    mtx.lock($);
    }
    }

    // does not really even need to be reversed...
    void
    unlock(
    ct_mutex_table& mutex_table
    ) {
    for (auto& mtx_idx : m_hashed_idxs)
    {
    rl::mutex& mtx = mutex_table.m_mutexs[mtx_idx];
    mtx.unlock($);
    }
    }
    };


    struct ct_state
    {
    ct_mutex_table m_mutex_table;
    VAR_T(int) m_var_0 = 0;
    VAR_T(int) m_var_1 = 1;
    VAR_T(int) m_var_2 = 2;


    void worker_thread_a()
    {
    ct_thread_mutex_hash self_hash;

    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_0));

    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_1));

    self_hash.finalize();

    self_hash.lock(m_mutex_table);

    VAR(m_var_0) = 42;
    VAR(m_var_1) = 128;

    self_hash.unlock(m_mutex_table);
    }

    void worker_thread_b()
    {
    ct_thread_mutex_hash self_hash;

    // Seed!
    {
    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_1));

    self_hash.m_hashed_idxs.push_back(
    m_mutex_table.hash_ptr(&m_var_0));
    }


    // Okay... Finalize it...
    {
    self_hash.finalize();
    }


    // Finally, we can lock the bastard!
    {
    self_hash.lock(m_mutex_table);

    {
    VAR(m_var_0) = 99;
    VAR(m_var_1) = 77;
    }

    self_hash.unlock(m_mutex_table);
    }
    }
    };


    struct ct_multex_relacy_test_v000
    : rl::test_suite<ct_multex_relacy_test_v000, CT_THREADS>
    {
    ct_state m_state = { };

    void before()
    {
    // not sure to init m_state here. Is it already init?
    }

    void
    thread(
    unsigned tidx
    ) {
    if (tidx == 0)
    m_state.worker_thread_a();
    else
    m_state.worker_thread_b();
    }
    };


    int main(int argc, char** argv)
    {
    {
    rl::test_params p;

    p.iteration_count = argc > 1 ? (unsigned)atoi(argv[1]) : 100000;
    p.execution_depth_limit = 100000;

    if (argc > 2) {
    std::string m = argv[2];
    if (m == "full") p.search_type = rl::sched_full;
    else if (m == "bound") { p.search_type = rl::sched_bound; p.context_bound = argc > 3 ? atoi(argv[3]) : 2; }
    }

    rl::simulate<ct_multex_relacy_test_v000>(p);
    }

    return 0;
    }



    /*
    #include <relacy/relacy.hpp>
    #include <iostream>


    int
    main()
    {
    std::cout << "ct_relacy_test\n";
    std::cout << "____________________________________________" <<
    std::endl;

    {

    }

    std::cout << "____________________________________________" <<
    std::endl;
    std::cout << "ct_relacy_test fin! :^)\n";

    return 0;
    }

    */



    --- 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 Nov 1 08:33:22 2026
    From Newsgroup: rec.arts.sf.written

    On Sat, 31 Oct 2026 13:11:29 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    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-a <already5chosen@yahoo.com> wrote:
    Only if you intended to close the TTY the programs were started
    on.-a 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".-a 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.


    What do you mean? Is the GUI deadlocking?

    What do I mean? If you don't understand the concepts of multithreading then maybe stay out of the discussion.

    --- 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 Nov 1 08:34:55 2026
    From Newsgroup: rec.arts.sf.written

    On Sat, 31 Oct 2026 13:14:47 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    If its multithreaded but that still happens someone probably has created
    too
    many critical sections with too many locks.


    Makes no sense at all. Have you taken a look at my multex? It can create

    WTF has your multex got to do with anything? No one was talking about your
    code so don't use this discussion as some excuse to show off some code you wrote than no one cares about.

    a shit lod of mutexes, and never deadlock. It keeps a strict locking
    order. Sorts and dedups the mutexes. Also, notice that an object does
    not need its own mutex:

    Thats nice.

    tl;dr

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 06:17:45 2026
    From Newsgroup: rec.arts.sf.written

    On 10/27/2026 3:45 AM, Michael S wrote:
    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.

    Wasn't that work done in preparation for the C++11 standard? I did not
    keep track of the standard's discussion, but presumably Microsoft had
    people both on the C++ standard's committee, and the Vista programming
    team.


    Best wishes, and happy standards!
    --
    Johann | email: invalid -> com | http://www.myrkraverk.com/blog/
    I'm not from the Internet, I just work there. | via Easynews.com https://bsky.app/profile/myrkraverk.bsky.social | for ( ;; ) _:;
    Federated at https://fed.brid.gy/bsky/myrkraverk.bsky.social
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 18:03:06 2026
    From Newsgroup: rec.arts.sf.written

    On 11/1/2026 1:33 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 13:11:29 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    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-a <already5chosen@yahoo.com> wrote:
    Only if you intended to close the TTY the programs were started >>>>>>>> on.-a 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".-a 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.


    What do you mean? Is the GUI deadlocking?

    What do I mean? If you don't understand the concepts of multithreading then maybe stay out of the discussion.


    Ummm. I think you are the one that does not know what the heck they are talking about.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 18:04:13 2026
    From Newsgroup: rec.arts.sf.written

    On 11/1/2026 1:34 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 13:14:47 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    If its multithreaded but that still happens someone probably has
    created too
    many critical sections with too many locks.


    Makes no sense at all. Have you taken a look at my multex? It can create

    WTF has your multex got to do with anything? No one was talking about your code so don't use this discussion as some excuse to show off some code you wrote than no one cares about.

    It uses a table of a lot of mutexes. Never deadlocks. So, you need to
    study up? You said "too many critical sections with too many locks."

    Well, if you don't know how to use them, don't use them. Learn first?


    a shit lod of mutexes, and never deadlock. It keeps a strict locking
    order. Sorts and dedups the mutexes. Also, notice that an object does
    not need its own mutex:

    Thats nice.

    tl;dr


    --- 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: rec.arts.sf.written

    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 Rosario19@Ros@invalid.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 10:58:51 2026
    From Newsgroup: rec.arts.sf.written

    On Tue, 20 Oct 2026 16:40:47 -0400, Cryptoengineer wrote:

    On 10/20/2026 2:22 PM, Scott Dorsey wrote:
    In article <11b8b2k$p44i$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>> Cryptoengineer <petertrei@gmail.com> wrote:
    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.

    I have seen a structured assembler class and it's actually not a bad way
    to think at all. Having LOOPZ and REP* and similar instructions make it
    easier to think about do loops.

    The key to writing structured assembly is commenting.

    The key to writing [] assembly is commenting.

    no it is the right code easy to understand
    comment can be avoid if someone use meaning varible (even if one char
    b= buffer, b=binary b=ebx ecc)

    Fixed That For You.

    pt


    --- 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 Nov 2 15:44:29 2026
    From Newsgroup: rec.arts.sf.written

    On Sun, 1 Nov 2026 18:03:06 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:33 AM, boltar@caprica.universe wrote:
    What do you mean? Is the GUI deadlocking?

    What do I mean? If you don't understand the concepts of multithreading then >> maybe stay out of the discussion.


    Ummm. I think you are the one that does not know what the heck they are >talking about.

    Yeah, ok. I've only been using pthreads for the last 25 years but sure, what
    do I know.

    --- 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 Nov 2 15:45:29 2026
    From Newsgroup: rec.arts.sf.written

    On Sun, 1 Nov 2026 18:04:13 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:34 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 13:14:47 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    If its multithreaded but that still happens someone probably has
    created too
    many critical sections with too many locks.


    Makes no sense at all. Have you taken a look at my multex? It can create >>
    WTF has your multex got to do with anything? No one was talking about your >> code so don't use this discussion as some excuse to show off some code you >> wrote than no one cares about.

    It uses a table of a lot of mutexes. Never deadlocks. So, you need to
    study up? You said "too many critical sections with too many locks."

    Well, if you don't know how to use them, don't use them. Learn first?

    I have no desire to spend hours trawling through someones pet project so they can make a point about what a L337 coder they are. HTH.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 14:33:41 2026
    From Newsgroup: rec.arts.sf.written

    On 11/2/2026 7:45 AM, boltar@caprica.universe wrote:
    On Sun, 1 Nov 2026 18:04:13 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:34 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 13:14:47 -0700
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 10/31/2026 2:38 AM, boltar@caprica.universe wrote:
    If its multithreaded but that still happens someone probably has
    created too
    many critical sections with too many locks.


    Makes no sense at all. Have you taken a look at my multex? It can
    create

    WTF has your multex got to do with anything? No one was talking about
    your
    code so don't use this discussion as some excuse to show off some
    code you
    wrote than no one cares about.

    It uses a table of a lot of mutexes. Never deadlocks. So, you need to
    study up? You said "too many critical sections with too many locks."

    Well, if you don't know how to use them, don't use them. Learn first?

    I have no desire to spend hours trawling through someones pet project so they
    can make a point about what a L337 coder they are. HTH.


    The code is not all that complicated?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 14:34:40 2026
    From Newsgroup: rec.arts.sf.written

    On 11/2/2026 7:44 AM, boltar@caprica.universe wrote:
    On Sun, 1 Nov 2026 18:03:06 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:33 AM, boltar@caprica.universe wrote:
    What do you mean? Is the GUI deadlocking?

    What do I mean? If you don't understand the concepts of
    multithreading then
    maybe stay out of the discussion.


    Ummm. I think you are the one that does not know what the heck they
    are talking about.

    Yeah, ok. I've only been using pthreads for the last 25 years but sure,
    what
    do I know.


    So you know what you wrote is odd wrt using too many mutexes? You
    snipped it out.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 14:54:48 2026
    From Newsgroup: rec.arts.sf.written

    On 11/1/2026 2:17 PM, Johann 'Myrkraverk' Oskarsson wrote:
    On 10/27/2026 3:45 AM, Michael S wrote:
    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.

    Wasn't that work done in preparation for the C++11 standard?-a I did not
    keep track of the standard's discussion, but presumably Microsoft had
    people both on the C++ standard's committee, and the Vista programming
    team.

    I think so.




    Best wishes, and happy standards!

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:38:55 2026
    From Newsgroup: rec.arts.sf.written

    On 10/22/2026 12:20 AM, David Brown wrote:
    [...]
    For the particular case of why C++ supports threads but not processes,
    the answer should be obvious.

    Indeed!

    --- Synchronet 3.22a-Linux NewsLink 1.2