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

    From Lynn McGuire@lynnmcguire5@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust on Thu Oct 15 14:13:32 2026
    From Newsgroup: comp.lang.fortran

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

    Because decompiling some languages isn't that hard. Humans can do it pretty well, although it's harder for machines. 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. 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. 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. Trying to get to 300,000 lines of Fortran 66/77 code
    before the end of the year.

    Lynn

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ted@loft.tnolan.com (Ted Nolan@tednolan to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust on Thu Oct 15 19:18:06 2026
    From Newsgroup: comp.lang.fortran

    In article <11ar89j$2mdpm$2@dont-email.me>,
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    On 10/15/2026 9:56 AM, Richard wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> spake the secret code
    <11amvre$15far$1@dont-email.me> thusly:

    Huh, so somebody has actually built a decent decompiler.

    It's been around for decades. It's called Ida Pro. The NSA published
    an open source one called Ghidra. It's actually not hard to recognize
    the output of a particular compiler and reverse engineer stack frames,
    arguments, etc.

    What the LLM brings to the picture is speculating meaningful
    datatypes, names, patterns, etc., on top of the mechanical
    decompilation.

    Why do I doubt
    this even though ESR says otherwise?

    Maybe because you don't have experience with existing reverse
    compilers (try Ghidra, since it's free) and LLMs?

    And he has a translator from Borland Pascal to Rust?

    It's not like he converted to Prolog. Mapping from one procedurally
    oriented block structured language to another is not particularly
    difficult.

    I tried Ida Pro several years ago. It was crap.

    I have never tried Ghidra. Maybe someday.


    Turbo Pascal was kind of amazing. Lightning fast compile on 8086, and
    ran on oddball hardware like the DEC Rainbow.
    --
    columbiaclosings.com
    What's not in Columbia anymore..
    --- 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 Thu Oct 15 15:02:12 2026
    From Newsgroup: comp.lang.fortran

    On 10/15/2026 2:18 PM, Ted Nolan <tednolan> wrote:
    In article <11ar89j$2mdpm$2@dont-email.me>,
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    On 10/15/2026 9:56 AM, Richard wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> spake the secret code
    <11amvre$15far$1@dont-email.me> thusly:

    Huh, so somebody has actually built a decent decompiler.

    It's been around for decades. It's called Ida Pro. The NSA published
    an open source one called Ghidra. It's actually not hard to recognize
    the output of a particular compiler and reverse engineer stack frames,
    arguments, etc.

    What the LLM brings to the picture is speculating meaningful
    datatypes, names, patterns, etc., on top of the mechanical
    decompilation.

    Why do I doubt
    this even though ESR says otherwise?

    Maybe because you don't have experience with existing reverse
    compilers (try Ghidra, since it's free) and LLMs?

    And he has a translator from Borland Pascal to Rust?

    It's not like he converted to Prolog. Mapping from one procedurally
    oriented block structured language to another is not particularly
    difficult.

    I tried Ida Pro several years ago. It was crap.

    I have never tried Ghidra. Maybe someday.


    Turbo Pascal was kind of amazing. Lightning fast compile on 8086, and
    ran on oddball hardware like the DEC Rainbow.

    Turbo Pascal was freaking AWESOME. The 1983 IDE (interactive
    development environment) was a revolutionary step ahead to this guy who started writing Fortran on key punch machines and a leased line 4800
    baud card reader / printer / teletype in 1975 connected to a Univac 1108.

    Lynn

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jay Morris@morrisj@epsilon3.me to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust on Thu Oct 15 20:35:40 2026
    From Newsgroup: comp.lang.fortran

    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.
    --- 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 18 09:20:51 2026
    From Newsgroup: comp.lang.fortran

    Scott Dorsey <kludge@panix.com> schrieb:
    Gary Scott <garylscott@sbcglobal.net> wrote:
    And you can write high quality code in Fortran more so with modern versions.

    I am not sure I agree with that. The matrix operations in f90 are wonderful and make compiler optimizations for vector machines so much easier. But pointers? Engineers should never be trusted with pointers.

    You hardly need pointers in modern Fortran. For very many, if
    not most, use cases allocatable variables do the job just fine,
    and the compiler does the memory management for you.
    --
    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 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 18 10:34:20 2026
    From Newsgroup: comp.lang.fortran

    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Gary Scott <garylscott@sbcglobal.net> wrote:
    And you can write high quality code in Fortran more so with modern versions. >>
    I am not sure I agree with that. The matrix operations in f90 are wonderful >> and make compiler optimizations for vector machines so much easier. But
    pointers? Engineers should never be trusted with pointers.

    You hardly need pointers in modern Fortran. For very many, if
    not most, use cases allocatable variables do the job just fine,
    and the compiler does the memory management for you.

    This is true. But that doesn't mean engineers won't use them. And they will put them in common blocks so they can store something as a pointer and then read it as an integer.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 Mon Oct 19 06:57:28 2026
    From Newsgroup: comp.lang.fortran

    Scott Dorsey <kludge@panix.com> schrieb:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Gary Scott <garylscott@sbcglobal.net> wrote:
    And you can write high quality code in Fortran more so with modern versions.

    I am not sure I agree with that. The matrix operations in f90 are wonderful
    and make compiler optimizations for vector machines so much easier. But >>> pointers? Engineers should never be trusted with pointers.

    You hardly need pointers in modern Fortran. For very many, if
    not most, use cases allocatable variables do the job just fine,
    and the compiler does the memory management for you.

    This is true. But that doesn't mean engineers won't use them. And they will put them in common blocks so they can store something as a pointer and then read it as an integer.

    Pointers in Fortran are more complicated than C pointers.
    For rank-0 (scalar) variables, they are usually implemented as
    addresses. For other ranks, bounds information is included. Plus,
    Fortran does not do address arithmetic on pointers like C or C++.

    But you can get at the internal representation of pointers via the
    TRANSFER function, or you can pass them via the C interoperability
    features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.
    --
    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 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 19 15:44:53 2026
    From Newsgroup: comp.lang.fortran

    Thomas Koenig <tkoenig@netcologne.de> wrote:
    But you can get at the internal representation of pointers via the
    TRANSFER function, or you can pass them via the C interoperability
    features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.

    Don't ask me, I just fix this stuff.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 Mon Oct 19 20:09:15 2026
    From Newsgroup: comp.lang.fortran

    Scott Dorsey <kludge@panix.com> schrieb:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    But you can get at the internal representation of pointers via the
    TRANSFER function, or you can pass them via the C interoperability >>features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.

    Don't ask me, I just fix this stuff.

    Do you actually encounter such code? Pointers in COMMON blocks
    sounds extremely weird. Or do you mean Cray pointers?
    Do you have an example?
    --
    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 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 19 13:09:45 2026
    From Newsgroup: comp.lang.fortran

    On 10/19/2026 12:44 PM, Scott Dorsey wrote:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    But you can get at the internal representation of pointers via the
    TRANSFER function, or you can pass them via the C interoperability
    features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.

    Don't ask me, I just fix this stuff.
    ;^D
    --- 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 19 16:10:33 2026
    From Newsgroup: comp.lang.fortran

    On 10/19/2026 3:09 PM, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    But you can get at the internal representation of pointers via the
    TRANSFER function, or you can pass them via the C interoperability
    features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.

    Don't ask me, I just fix this stuff.

    Do you actually encounter such code? Pointers in COMMON blocks
    sounds extremely weird. Or do you mean Cray pointers?
    Do you have an example?

    We have thousands of C pointers stored in Fortran common blocks. That
    is one of the many reasons that I am converting my simulation software
    to C++.

    Lynn

    --- 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 19 18:08:25 2026
    From Newsgroup: comp.lang.fortran

    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    But you can get at the internal representation of pointers via the >>>TRANSFER function, or you can pass them via the C interoperability >>>features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.

    Don't ask me, I just fix this stuff.

    Do you actually encounter such code? Pointers in COMMON blocks
    sounds extremely weird. Or do you mean Cray pointers?

    I encounter a LOT of code written by engineers who think they know about
    new language features but don't really.

    But what they lose in missing comments, they make up for in spurious gotos. --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 19 17:10:58 2026
    From Newsgroup: comp.lang.fortran

    On 10/19/2026 5:08 PM, Scott Dorsey wrote:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    But you can get at the internal representation of pointers via the
    TRANSFER function, or you can pass them via the C interoperability
    features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.

    Don't ask me, I just fix this stuff.

    Do you actually encounter such code? Pointers in COMMON blocks
    sounds extremely weird. Or do you mean Cray pointers?

    I encounter a LOT of code written by engineers who think they know about
    new language features but don't really.

    But what they lose in missing comments, they make up for in spurious gotos. --scott

    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos. The remaining 25% Gotos usually make some sense.
    Ok, a little sense that any C or C++ programmer would have never used a
    goto there.

    Lynn

    --- 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 19 16:26:07 2026
    From Newsgroup: comp.lang.fortran

    Scott Dorsey wrote:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    But you can get at the internal representation of pointers via the
    TRANSFER function, or you can pass them via the C interoperability
    features.

    Putting them in COMMON blocks and then accessing them via type
    punning would be a useless thing to do.

    Don't ask me, I just fix this stuff.

    Do you actually encounter such code? Pointers in COMMON blocks
    sounds extremely weird. Or do you mean Cray pointers?

    I encounter a LOT of code written by engineers who think they know about
    new language features but don't really.

    But what they lose in missing comments, they make up for in spurious gotos. --scott

    Jim Geekie, EE, was my mate in graduate school. We also attended the
    same undergraduate university. He was quite averse to code. He decided
    to take a job offer before even completing his masters.

    Jay, CE, was my mate in graduate school. We also attended the same undergraduate university. He was content to let me write the entire web browser for Microcomputers class. I think I paused from time to time in
    case he was going to write something but I went ahead. Unfortunately I
    had a big error: e.g. I thought you could do -7 % 10 and it would give
    you +3. Unfortunately at the time, a % b in c returns negative for
    negative a, except maybe in some zero cases.

    I'm an engineer, but I completed a minor in computer science. I also was aiming high for a double major, including CS, but course load knocked me
    on my ass senior year.

    I broke this habit of writing the entire project in my second group
    project at Northface University (now Neumont College in SLC, UT). After
    doing the entire first project myself, and getting embarrassed when one
    of the teachers mocked me for a small part of it, I was ready to work as
    a team on the second project.

    I guess I take umbrage at your goto statement. I do nothing of the like.
    --
    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 19 18:57:58 2026
    From Newsgroup: comp.lang.fortran

    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos. The remaining 25% Gotos usually make some sense.
    Ok, a little sense that any C or C++ programmer would have never used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do loop.
    The compiler is doing so much cleanup work that the programmer never sees. --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 Mon Oct 19 19:01:36 2026
    From Newsgroup: comp.lang.fortran

    Blaine <cactus_DAC@yahoo.com> wrote:
    I guess I take umbrage at your goto statement. I do nothing of the like.

    It gets worse than that.

    groovy:: ; do that groovy thing
    .call_entry max_args=33,home_args=true,preserve=<r3,r5>
    movl (ap),r3 ; boogity boogity boogity
    moval 4(ap),r5 ; yeah, you got it baby
    ret ; go back and do it again
    .psect idata,wrt,noexe,quad
    .align quad

    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 Tue Oct 20 05:28:40 2026
    From Newsgroup: comp.lang.fortran

    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>Ok, a little sense that any C or C++ programmer would have never used a >>goto there.

    It drives me up the wall when people use a goto to jump out of a do loop.
    The compiler is doing so much cleanup work that the programmer never sees.

    Again, care to give an example?
    --
    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 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 20 18:46:04 2026
    From Newsgroup: comp.lang.fortran

    On 20/10/2026 18:28, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>> Ok, a little sense that any C or C++ programmer would have never used a >>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop.
    The compiler is doing so much cleanup work that the programmer never sees.

    Again, care to give an example?

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.
    --- 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 Tue Oct 20 00:48:50 2026
    From Newsgroup: comp.lang.fortran

    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos. The remaining 25% Gotos usually make some sense.
    Ok, a little sense that any C or C++ programmer would have never used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do loop.
    The compiler is doing so much cleanup work that the programmer never sees. --scott

    Why do you care about unseen work that the compiler is doing? I
    guarantee that most programmers in these 64 bit days do not care.

    Lynn

    --- 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 Tue Oct 20 09:39:00 2026
    From Newsgroup: comp.lang.fortran

    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos. The remaining 25% Gotos usually make some sense.
    Ok, a little sense that any C or C++ programmer would have never used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do loop.
    The compiler is doing so much cleanup work that the programmer never sees.

    Why do you care about unseen work that the compiler is doing? I
    guarantee that most programmers in these 64 bit days do not care.

    Because I want my code to run fast! I do very much seem to be in the
    minority today, it is true.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 Tue Oct 20 21:51:22 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 9:39 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>> Ok, a little sense that any C or C++ programmer would have never used a >>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>> The compiler is doing so much cleanup work that the programmer never sees. >>
    Why do you care about unseen work that the compiler is doing? I
    guarantee that most programmers in these 64 bit days do not care.

    Because I want my code to run fast! I do very much seem to be in the minority today, it is true.
    --scott

    I presume you're working on some /hot code/, and will comment according-
    ly.

    I've come across complaints -- that I don't have handy -- that compilers sometimes under-optimize, or otherwise cannot be told to do the right
    thing. One memorable complaint was the inability of then-GCC to align
    a specific loop to the cache -- I believe a 16 byte boundary -- it was
    only everything -- with the resulting drop in performance everywhere
    else -- or nothing because there was no #pragma nor [[attribute]] to say
    /this loop needs to be cache aligned/.


    What do you do in these circumstances? Has this happened to you at all?
    --
    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 Thomas Koenig@tkoenig@netcologne.de to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 15:50:23 2026
    From Newsgroup: comp.lang.fortran

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> schrieb:

    I've come across complaints -- that I don't have handy -- that compilers sometimes under-optimize, or otherwise cannot be told to do the right
    thing.

    https://gcc.gnu.org/bugzilla/buglist.cgi?bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=SUSPENDED&bug_status=WAITING&bug_status=REOPENED&cf_known_to_fail_type=allwords&cf_known_to_work_type=allwords&keywords=missed-optimization%2C%20&keywords_type=allwords&limit=0&list_id=536399&order=priority%2Cbug_severity&query_format=advanced

    gives you (as of now) 4588 exammples.
    --
    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 Thomas Koenig@tkoenig@netcologne.de to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 17:15:28 2026
    From Newsgroup: comp.lang.fortran

    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos. The remaining 25% Gotos usually make some sense.
    Ok, a little sense that any C or C++ programmer would have never used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do loop.
    The compiler is doing so much cleanup work that the programmer never sees.

    I'd really like to know what that cleanup work is supposed to be (as
    somebody who is involved with Fortran compiler development).

    I am beginning to suspect that Scott is the only person in the
    world who sees this supposed inefficiency.

    --scott

    Why do you care about unseen work that the compiler is doing? I
    guarantee that most programmers in these 64 bit days do not care.

    For very many problems, there is no need to be efficient - it very
    certainly does not matter if a program that is executed once takes
    0.01 s or 0.1s.

    But the attitude of not caring about speed can have grave results
    when the inefficiencies pile up. People who use Python for
    everything may find that instead of 0.1 s, their code suddenly
    runs for hours, when it would need seconds in a compiled language.

    Or look at the pile of resource-wasting junk like Microsoft
    Teams runnig on top of the pile of resource-wasting junk called
    Microsoft Windows. Teams grabs a humungous amount of memory so 16
    GB is borderline unusable in a commercial enviroment. Makes the
    recent memory price hike all the more interesting...

    Don't know about your code, but I remember waiting a long time
    for Aspen simulations... but then again, those diverge from
    a converged solution, which shows that if Aspen has the first
    clue about numerical methods, they are very good at hiding it.

    I just hope your software is better, at least in that respect.
    --
    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 Cryptoengineer@petertrei@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 13:20:40 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 1:46 AM, Titus G wrote:
    On 20/10/2026 18:28, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>> Ok, a little sense that any C or C++ programmer would have never used a >>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>> The compiler is doing so much cleanup work that the programmer never sees. >>
    Again, care to give an example?

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf

    pt
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 17:24:27 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 17:15:28 -0000 (UTC)
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>> Ok, a little sense that any C or C++ programmer would have never used a >>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>> The compiler is doing so much cleanup work that the programmer never sees.

    I'd really like to know what that cleanup work is supposed to be (as
    somebody who is involved with Fortran compiler development).

    If C/C++ had multi level break and continue keywords goto would almost
    never be needed**. There's no reason they can't be added - along with a lot of other useful but basic fatures (eg non POD switch, native concatting numbers to
    std::string without calling to_string) - but I guess the committee are too busy circle jerking with esoteric crap no one will ever use (eg concepts) to bother.

    ** The setting a flag method which has to be checked in every nested loop test
    is just an assinine way to code.

    --- 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 Wed Oct 21 01:27:56 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/2026 1:20 AM, Cryptoengineer wrote:
    On 10/20/2026 1:46 AM, Titus G wrote:
    On 20/10/2026 18:28, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire-a <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>>> of the Fortran Gotos.-a The remaining 25% Gotos usually make some
    sense.
    Ok, a little sense that any C or C++ programmer would have never
    used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do
    loop.
    The compiler is doing so much cleanup work that the programmer never
    sees.

    Again, care to give an example?

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf

    pt

    Some people think Michael Jackson invented structured programming, but
    he merely wrote about it.

    https://en.wikipedia.org/wiki/Jackson_structured_programming

    I admit not to have gotten myself a copy of /Principles of Program
    Design/ but it's on my to-be-tsundoku list.


    Best wishes, and happy structured programming!
    --
    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@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 18:14:44 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 13:20:40 -0400
    Cryptoengineer <petertrei@gmail.com> wrote:
    On 10/20/2026 1:46 AM, Titus G wrote:
    On 20/10/2026 18:28, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>>> Ok, a little sense that any C or C++ programmer would have never used a >>>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>>> The compiler is doing so much cleanup work that the programmer never sees. >>>
    Again, care to give an example?

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.

    --- 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 Tue Oct 20 14:22:02 2026
    From Newsgroup: comp.lang.fortran

    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.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 18:29:37 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 14:22:02 -0400 (EDT)
    kludge@panix.com (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.

    Great if the cpu supports those sorts of instructions. Most however rely
    on some version of jump-on-flag-set/not-set for flow of control apart from call-ret.

    --- 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 Tue Oct 20 14:36:11 2026
    From Newsgroup: comp.lang.fortran

    Cryptoengineer wrote:
    On 10/20/2026 1:46 AM, Titus G wrote:
    On 20/10/2026 18:28, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire-a <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>>> of the Fortran Gotos.-a The remaining 25% Gotos usually make some
    sense.
    Ok, a little sense that any C or C++ programmer would have never
    used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do
    loop.
    The compiler is doing so much cleanup work that the programmer never
    sees.

    Again, care to give an example?

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf

    First year computer science prof:

    "When I first learned to program I thanked god for the goto statement.
    Now I hate the very sight of it".

    Luckily I took German instead.

    My own code was liberally festooned with goto statments, but as far as I
    can recall I never put a pointer in common.

    Using goto to exit loops? I can't recall doing that. But I can't rule
    it out.

    William Hyde

    --- 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 Tue Oct 20 14:48:02 2026
    From Newsgroup: comp.lang.fortran

    Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>> Ok, a little sense that any C or C++ programmer would have never used a >>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>> The compiler is doing so much cleanup work that the programmer never sees. >>
    Why do you care about unseen work that the compiler is doing? I
    guarantee that most programmers in these 64 bit days do not care.

    Because I want my code to run fast! I do very much seem to be in the minority today, it is true.

    We simply didn't have the computer resources to run my PhD code
    normally. I spoke to more experienced programmers and learned many
    tricks to speed things up. This probably knocked a year off my PhD, to
    the great benefit of my sanity and financial health.

    And in climate modelling, these tricks proved useful again and again. A
    month spent optimizing code could save a year on a big project. We were
    always pushing the limits of whatever our computers could do.


    The first general circulation model I worked with was a spectral model
    using spherical harmonics out to order twenty or so. The last went to
    order 178. Give us a faster computer and we'll bog it down immediately.

    Mind you the movie of the T178 storm tracks in the last ice age was a
    wonder to behold.

    As a coder I was at best 3/10 in scientific code. At accelerating
    scientific code, maybe 5.

    At game development, 0.01.

    William Hyde

    --- 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 20 20:50:58 2026
    From Newsgroup: comp.lang.fortran

    On 20/10/2026 19:24, boltar@battlestar.co.uk wrote:
    On Tue, 20 Oct 2026 17:15:28 -0000 (UTC)
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>>> Ok, a little sense that any C or C++ programmer would have never used a >>>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>>> The compiler is doing so much cleanup work that the programmer never sees. >>
    I'd really like to know what that cleanup work is supposed to be (as
    somebody who is involved with Fortran compiler development).

    If C/C++ had multi level break and continue keywords goto would almost
    never be needed**. There's no reason they can't be added - along with a lot of
    other useful but basic fatures (eg non POD switch, native concatting numbers to
    std::string without calling to_string) - but I guess the committee are too busy
    circle jerking with esoteric crap no one will ever use (eg concepts) to bother.


    Multi-level break and continue (named loops) is on its way to C++, and
    will almost certainly be accepted sooner or later (since it is already
    in the draft of the next C standard):

    <https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3568r0.html>

    And people /do/ use concepts, even if you do not.

    You might want to do some research before insulting the people who are actually doing the work in driving languages forward.

    --- 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 Tue Oct 20 19:04:55 2026
    From Newsgroup: comp.lang.fortran

    On 2026-10-20, boltar@battlestar.co.uk <boltar@battlestar.co.uk> wrote:

    On Tue, 20 Oct 2026 13:20:40 -0400

    Cryptoengineer <petertrei@gmail.com> wrote:

    On 10/20/2026 1:46 AM, Titus G wrote:

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.

    Of course. He was a CS weenie - any mention of low-level
    programming makes those types turn purple.

    Although Structured Programming introduced some good concepts,
    it also built a following of fanatics more bent on crucifying
    infidels than writing good practical programs. Some people
    came to see the number of function calls a program made as
    a figure of merit, resulting in dozens of tiny functions that
    caused control to jump all over the place (which made virtual
    memory systems thrash). And the end result wasn't that much
    more readable.

    The undisciplined use of GOTOs is bad, agreed. But the
    undisciplined use of function calls isn't a whole lot better.
    After all, a function call is just a GOTO paired with a
    "come from", so in the end it's all still spaghetti code -
    it's just that the "structured" code runs double strands.
    --
    /~\ 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 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 Tue Oct 20 12:10:14 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/26 10:15, Thomas Koenig wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>> Ok, a little sense that any C or C++ programmer would have never used a >>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>> The compiler is doing so much cleanup work that the programmer never sees.

    I'd really like to know what that cleanup work is supposed to be (as
    somebody who is involved with Fortran compiler development).

    I am beginning to suspect that Scott is the only person in the
    world who sees this supposed inefficiency.

    --scott

    Why do you care about unseen work that the compiler is doing? I
    guarantee that most programmers in these 64 bit days do not care.

    For very many problems, there is no need to be efficient - it very
    certainly does not matter if a program that is executed once takes
    0.01 s or 0.1s.

    But the attitude of not caring about speed can have grave results
    when the inefficiencies pile up. People who use Python for
    everything may find that instead of 0.1 s, their code suddenly
    runs for hours, when it would need seconds in a compiled language.

    Or look at the pile of resource-wasting junk like Microsoft
    Teams runnig on top of the pile of resource-wasting junk called
    Microsoft Windows. Teams grabs a humungous amount of memory so 16
    GB is borderline unusable in a commercial enviroment. Makes the
    recent memory price hike all the more interesting...

    Don't know about your code, but I remember waiting a long time
    for Aspen simulations... but then again, those diverge from
    a converged solution, which shows that if Aspen has the first
    clue about numerical methods, they are very good at hiding it.

    I just hope your software is better, at least in that respect.


    If there is any work to do, the compiler should also be able to do it in
    the case of a GOTO out of a loop.
    --- 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 Tue Oct 20 12:11:33 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/26 10:24, boltar@battlestar.co.uk wrote:
    On Tue, 20 Oct 2026 17:15:28 -0000 (UTC)
    Thomas Koenig <tkoenig@netcologne.de> wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>>> Ok, a little sense that any C or C++ programmer would have never used a >>>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>>> The compiler is doing so much cleanup work that the programmer never sees. >>
    I'd really like to know what that cleanup work is supposed to be (as
    somebody who is involved with Fortran compiler development).

    If C/C++ had multi level break and continue keywords goto would almost
    never be needed**. There's no reason they can't be added - along with a lot of
    other useful but basic fatures (eg non POD switch, native concatting numbers to
    std::string without calling to_string) - but I guess the committee are too busy
    circle jerking with esoteric crap no one will ever use (eg concepts) to bother.

    ** The setting a flag method which has to be checked in every nested loop test
    is just an assinine way to code.

    They just keep trying to re-invert PL/I.
    --- 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 Tue Oct 20 19:54:22 2026
    From Newsgroup: comp.lang.fortran

    Charlie Gibbs <cgibbs@kltpzyxm.invalid> schrieb:
    On 2026-10-20, boltar@battlestar.co.uk <boltar@battlestar.co.uk> wrote:

    On Tue, 20 Oct 2026 13:20:40 -0400

    Cryptoengineer <petertrei@gmail.com> wrote:

    On 10/20/2026 1:46 AM, Titus G wrote:

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.

    Of course. He was a CS weenie - any mention of low-level
    programming makes those types turn purple.

    Nonsense.

    Dijstra started programming in 1951, they didn't even have
    assemblers on the machines, it was pretty much naked machine code.

    Whatever else his faults may have been (arrogance certainly being
    among them), he was no stranger to low-level programming.
    --
    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 20:00:03 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 19:04:55 GMT, Charlie Gibbs wrote:

    The undisciplined use of GOTOs is bad, agreed.

    Is there such a thing as a *disciplined* use of gotos?

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error recovery
    will invariably involve cleaning up those parts of the allocations
    which already succeeded. Gotos are no good for this; you need to exit
    levels of structure nesting one by one, disposing of allocations as
    you go.

    I put together an example here <https://gitlab.com/ldo/a_structured_discipline_of_programming>. This
    is an extension module that offers services to Python code, because
    that is just about the worst example I could think of, for those who
    think gotos can cut it.
    --- 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 Tue Oct 20 15:06:48 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 1: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.
    --scott

    The key to writing any software is lots of commenting.

    About a third of my calculation engine was written pre 1978 (250,000
    lines of Fortran 66 code) and that code cost us money to sit on a drum
    drive on a Univac 1108. So no comments for that code except where
    somebody came along and threw something in there after 1977. Sometimes
    the later comments are correct, sometimes the later comments are wrong.

    Lynn

    --- 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 Tue Oct 20 15:20:29 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 12:15 PM, Thomas Koenig wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>> Ok, a little sense that any C or C++ programmer would have never used a >>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>> The compiler is doing so much cleanup work that the programmer never sees.

    I'd really like to know what that cleanup work is supposed to be (as
    somebody who is involved with Fortran compiler development).

    I am beginning to suspect that Scott is the only person in the
    world who sees this supposed inefficiency.

    --scott

    Why do you care about unseen work that the compiler is doing? I
    guarantee that most programmers in these 64 bit days do not care.

    For very many problems, there is no need to be efficient - it very
    certainly does not matter if a program that is executed once takes
    0.01 s or 0.1s.

    But the attitude of not caring about speed can have grave results
    when the inefficiencies pile up. People who use Python for
    everything may find that instead of 0.1 s, their code suddenly
    runs for hours, when it would need seconds in a compiled language.

    Or look at the pile of resource-wasting junk like Microsoft
    Teams runnig on top of the pile of resource-wasting junk called
    Microsoft Windows. Teams grabs a humungous amount of memory so 16
    GB is borderline unusable in a commercial enviroment. Makes the
    recent memory price hike all the more interesting...

    Don't know about your code, but I remember waiting a long time
    for Aspen simulations... but then again, those diverge from
    a converged solution, which shows that if Aspen has the first
    clue about numerical methods, they are very good at hiding it.

    I just hope your software is better, at least in that respect.

    Most of our convergence methods use Newton-Raphson, yes that Isaac
    Newton, to start, very quick to solve if it solves. If that spirals out
    of control then we use the halving method, brute force and very slow.
    If that fails then we use an interpolation method, also very slow. If
    that fails (the flash is infeasible), then we report the failure to the
    user.

    Our rigorous four phase flash is the worst since it solves two sets of k-values simultaneously with a vapor-liquid-solid fugacity based solid
    flash. The four phases are vapor, hydrocarbon liquid, aqueous liquid,
    and solid. Almost 300,000 lines of Fortran 66/77 code that I am
    converting to C++.

    And there are exceptions all over the place to the above since our
    software is Frankenstein consisting of the Design, Distill, Refine, and Gasplant Plus programs merged together.

    Lynn

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

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is
    doing what itrCOs doing, not simply repeat *what* it is doing. E.g.

    watcher = inotify.Watcher.create()
    watching = {}
    # Monitor immediate containing directories for possibility of files
    # disappearing, assuming those directories will not themselves disappear!
    FILE_EVENTS = \
    { # watch for the file itself changing or disappearing
    IN_BIT.CLOSE_WRITE,
    IN_BIT.DELETE_SELF,
    IN_BIT.MOVE_SELF,
    IN_BIT.MASK_CREATE, # files mustnrCOt be the same!
    }
    for key in path_keys :
    path = config[key]
    parent = os.path.dirname(path) # assumes I donrCOt need to normalize path
    watching[path] = watcher.watch(path, FILE_EVENTS)
    # plus a watch on parent directory for disappeared file coming back:
    # (This wonrCOt work if file was symlinked; do I care?)
    if parent not in watching :
    # files will typically be in same directory
    watching[parent] = watcher.watch \
    (
    parent,
    {IN_BIT.CREATE, IN_BIT.MOVED_TO, IN_BIT.ONLYDIR}
    )
    #end if
    #end for
    --- 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 Tue Oct 20 16:40:47 2026
    From Newsgroup: comp.lang.fortran

    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.

    Fixed That For You.

    pt


    --- 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 Tue Oct 20 16:41:43 2026
    From Newsgroup: comp.lang.fortran

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    On 10/20/2026 9:39 PM, Scott Dorsey wrote:
    Because I want my code to run fast! I do very much seem to be in the
    minority today, it is true.

    I presume you're working on some /hot code/, and will comment according-
    ly.

    It's not super hot, but it's often pretty dense dsp stuff and requires extensive commenting to describe exactly what equations are for and how
    they are being used.

    Unfortunately so much of the code I deal with has comments like

    C BRAINDAMAGE! ROCKWELL-COLLINS BRAINDAMAGE!

    Which are expressive and they are good warnings that something is about
    to follow which has to do with hardware design deficiencies but not
    actually very informative about what they are.

    I've come across complaints -- that I don't have handy -- that compilers >sometimes under-optimize, or otherwise cannot be told to do the right
    thing. One memorable complaint was the inability of then-GCC to align
    a specific loop to the cache -- I believe a 16 byte boundary -- it was
    only everything -- with the resulting drop in performance everywhere
    else -- or nothing because there was no #pragma nor [[attribute]] to say >/this loop needs to be cache aligned/.

    There used to be a lot of complaints like that around here, but these
    days gcc is so much better than it was even a decade ago. The new
    gfortran is not perfect but it's entirely acceptable and takes advantage
    of the good backend developed for gcc. The older g77 was excruciating.
    I'd read the .a files that came out and just want to hit my head on the
    desk.

    What do you do in these circumstances? Has this happened to you at all?

    I go home and I have a drink and I try not to think about it. Yes, it
    could run a lot better but....
    --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 Tue Oct 20 20:49:28 2026
    From Newsgroup: comp.lang.fortran

    boltar@battlestar.co.uk writes:
    On Tue, 20 Oct 2026 13:20:40 -0400
    Cryptoengineer <petertrei@gmail.com> wrote:
    On 10/20/2026 1:46 AM, Titus G wrote:
    On 20/10/2026 18:28, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>>>> of the Fortran Gotos. The remaining 25% Gotos usually make some sense. >>>>>> Ok, a little sense that any C or C++ programmer would have never used a >>>>>> goto there.

    It drives me up the wall when people use a goto to jump out of a do loop. >>>>> The compiler is doing so much cleanup work that the programmer never sees.

    Again, care to give an example?

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.


    Actually, it's highly likely he did program in assembler.

    He was a Burroughs fellow for a decade however, working
    on the large systems family which did not have an
    assembler - flavors of Algol were the only way to write
    systems (e.g. MCP) code.

    --- 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 Tue Oct 20 16:49:30 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 3:04 PM, Charlie Gibbs wrote:
    On 2026-10-20, boltar@battlestar.co.uk <boltar@battlestar.co.uk> wrote:

    On Tue, 20 Oct 2026 13:20:40 -0400

    Cryptoengineer <petertrei@gmail.com> wrote:

    On 10/20/2026 1:46 AM, Titus G wrote:

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.

    Of course. He was a CS weenie - any mention of low-level
    programming makes those types turn purple.


    There was one time when I wrote 6502 assembler including
    self-modifying code. That would have made them turn
    ultraviolet.

    The 6502 had some indexed load and store instructions, where
    the instruction contained a base address, which was indexed
    with a register. To deal with a big array (bitmap of the
    Apple ][ HIRES screen), I wrote code that modified the base
    address in the instruction. Of course, I was careful to
    reset it when done.

    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 Tue Oct 20 17:03:13 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 1:48 AM, Lynn McGuire wrote:
    On 10/19/2026 5:57 PM, Scott Dorsey wrote:
    Lynn McGuire-a <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75%
    of the Fortran Gotos.-a The remaining 25% Gotos usually make some sense. >>> Ok, a little sense that any C or C++ programmer would have never used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do loop.
    The compiler is doing so much cleanup work that the programmer never
    sees.
    --scott

    Why do you care about unseen work that the compiler is doing?-a I
    guarantee that most programmers in these 64 bit days do not care.

    One side project I worked on at RSA (managing a crowd sourced
    effort to crack symmetric keys to push policy on exportable
    key length) used literal years of cpu time. Optimizing the code
    was paramount.

    At one point, I had the world's fastest implementation of the
    DES algorithm, though I was soon beaten.

    pt
    --- 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 Tue Oct 20 21:20:02 2026
    From Newsgroup: comp.lang.fortran

    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/20/2026 12:15 PM, Thomas Koenig wrote:

    Don't know about your code, but I remember waiting a long time
    for Aspen simulations... but then again, those diverge from
    a converged solution, which shows that if Aspen has the first
    clue about numerical methods, they are very good at hiding it.

    I just hope your software is better, at least in that respect.

    Most of our convergence methods use Newton-Raphson, yes that Isaac
    Newton, to start, very quick to solve if it solves. If that spirals out
    of control then we use the halving method, brute force and very slow.
    If that fails then we use an interpolation method, also very slow. If
    that fails (the flash is infeasible), then we report the failure to the user.

    Sounds reasonable, but...

    How can bisection fail? If you have bracketed your roots and
    have no singularities it always succeeds.

    Hmm... molar fractions less than zero, maybe?

    Our rigorous four phase flash is the worst since it solves two sets of k-values simultaneously with a vapor-liquid-solid fugacity based solid flash. The four phases are vapor, hydrocarbon liquid, aqueous liquid,
    and solid. Almost 300,000 lines of Fortran 66/77 code that I am
    converting to C++.

    For two variables, of course, bisection will not work.

    And there are exceptions all over the place to the above since our
    software is Frankenstein consisting of the Design, Distill, Refine, and Gasplant Plus programs merged together.

    I can imagine...
    --
    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 Lynn McGuire@lynnmcguire5@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 16:26:00 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 4:20 PM, Thomas Koenig wrote:
    Lynn McGuire <lynnmcguire5@gmail.com> schrieb:
    On 10/20/2026 12:15 PM, Thomas Koenig wrote:

    Don't know about your code, but I remember waiting a long time
    for Aspen simulations... but then again, those diverge from
    a converged solution, which shows that if Aspen has the first
    clue about numerical methods, they are very good at hiding it.

    I just hope your software is better, at least in that respect.

    Most of our convergence methods use Newton-Raphson, yes that Isaac
    Newton, to start, very quick to solve if it solves. If that spirals out
    of control then we use the halving method, brute force and very slow.
    If that fails then we use an interpolation method, also very slow. If
    that fails (the flash is infeasible), then we report the failure to the
    user.

    Sounds reasonable, but...

    How can bisection fail? If you have bracketed your roots and
    have no singularities it always succeeds.

    Hmm... molar fractions less than zero, maybe?

    Our rigorous four phase flash is the worst since it solves two sets of
    k-values simultaneously with a vapor-liquid-solid fugacity based solid
    flash. The four phases are vapor, hydrocarbon liquid, aqueous liquid,
    and solid. Almost 300,000 lines of Fortran 66/77 code that I am
    converting to C++.

    For two variables, of course, bisection will not work.

    And there are exceptions all over the place to the above since our
    software is Frankenstein consisting of the Design, Distill, Refine, and
    Gasplant Plus programs merged together.

    I can imagine...

    An infeasible problem is impossible to solve but it has to go through
    all of the solvers before it is declared to be infeasible. We have some quality analysis (Michelson, et al) but if you do quality analysis, you
    have solved most of the problem already.

    Lynn

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 23:18:44 2026
    From Newsgroup: comp.lang.fortran

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

    On Tue, 20 Oct 2026 19:04:55 GMT, Charlie Gibbs wrote:

    The undisciplined use of GOTOs is bad, agreed.

    Is there such a thing as a *disciplined* use of gotos?

    Yes, especially in COBOL or assembly language. For instance,
    a GOTO to the end of a function ensures any of its cleanup code
    gets executed, and fulfils a goal of structured proramming:
    each function has one exit point.

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error recovery
    will invariably involve cleaning up those parts of the allocations
    which already succeeded. Gotos are no good for this; you need to exit
    levels of structure nesting one by one, disposing of allocations as
    you go.

    I know that a lot of CS types are going to stick pins into little
    dolls that look like me for saying this, but IMHO resource pointers,
    handles, etc. should be global. Possible exceptions are resources
    that are going to be used solely by the current function - but even
    then, if that function calls another function that fails horribly,
    there's stuff that might not get cleaned up. That's why all my
    C programs contain a function quit_cleanup(char *errmsg), which
    de-allocates all resources and then exits (displaying "errmsg"
    if it isn't NULL). I can call that function anywhere, safe in
    the knowledge that by the time it finishes (it never returns),
    everything will have be freed.
    --
    /~\ 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 Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 23:20:58 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 20:00:03 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Tue, 20 Oct 2026 19:04:55 GMT, Charlie Gibbs wrote:

    The undisciplined use of GOTOs is bad, agreed.

    Is there such a thing as a *disciplined* use of gotos?


    Yes. D. Knuth, Structured Programming with go to Statements,
    ACM Computing Surveys (CSUR), Vol 6, Issue 4, Pp 261-301, 1974 https://doi.org/10.1145/356635.356640
    --
    steve
    --- 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 Tue Oct 20 19:32:28 2026
    From Newsgroup: comp.lang.fortran

    Lynn McGuire wrote:
    On 10/20/2026 1:22 PM, Scott Dorsey wrote:
    In article <11b8b2k$p44i$1@dont-email.me>,-a <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.-a Having LOOPZ and REP* and similar instructions make it
    easier to think about do loops.

    The key to writing structured assembly is commenting.
    --scott

    The key to writing any software is lots of commenting.

    About a third of my calculation engine was written pre 1978 (250,000
    lines of Fortran 66 code) and that code cost us money to sit on a drum
    drive on a Univac 1108.-a So no comments for that code except where
    somebody came along and threw something in there after 1977.-a Sometimes
    the later comments are correct, sometimes the later comments are wrong.

    Ah, I do love zombie comments, where someone has changed the code but
    left the comments as they were.

    It's my favourite source of new curses.

    William Hyde

    --- 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 Tue Oct 20 16:48:02 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 1:41 PM, Scott Dorsey wrote:
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    On 10/20/2026 9:39 PM, Scott Dorsey wrote:
    Because I want my code to run fast! I do very much seem to be in the
    minority today, it is true.

    I presume you're working on some /hot code/, and will comment according-
    ly.

    It's not super hot, but it's often pretty dense dsp stuff and requires extensive commenting to describe exactly what equations are for and how
    they are being used.

    Unfortunately so much of the code I deal with has comments like

    C BRAINDAMAGE! ROCKWELL-COLLINS BRAINDAMAGE!

    Which are expressive and they are good warnings that something is about
    to follow which has to do with hardware design deficiencies but not
    actually very informative about what they are.

    I've come across complaints -- that I don't have handy -- that compilers
    sometimes under-optimize, or otherwise cannot be told to do the right
    thing. One memorable complaint was the inability of then-GCC to align
    a specific loop to the cache -- I believe a 16 byte boundary -- it was
    only everything -- with the resulting drop in performance everywhere
    else -- or nothing because there was no #pragma nor [[attribute]] to say
    /this loop needs to be cache aligned/.

    There used to be a lot of complaints like that around here, but these
    days gcc is so much better than it was even a decade ago. The new
    gfortran is not perfect but it's entirely acceptable and takes advantage
    of the good backend developed for gcc. The older g77 was excruciating.
    I'd read the .a files that came out and just want to hit my head on the
    desk.

    What do you do in these circumstances? Has this happened to you at all?

    I go home and I have a drink and I try not to think about it. Yes, it
    could run a lot better but....
    A drink? Ahh some brain coolants. Well, they are needed from time to
    time... ;^D
    --- 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.comp.lang.rust,alt.folklore.computers on Wed Oct 21 01:15:25 2026
    From Newsgroup: comp.lang.fortran

    On 2026-10-20, Charlie Gibbs wrote:

    On 2026-10-20, boltar@battlestar.co.uk <boltar@battlestar.co.uk> wrote:

    On Tue, 20 Oct 2026 13:20:40 -0400

    Cryptoengineer <petertrei@gmail.com> wrote:

    On 10/20/2026 1:46 AM, Titus G wrote:

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    A man who clearly never programmed in assembler.

    Of course. He was a CS weenie - any mention of low-level
    programming makes those types turn purple.

    Although Structured Programming introduced some good concepts,
    it also built a following of fanatics more bent on crucifying
    infidels than writing good practical programs. Some people
    came to see the number of function calls a program made as
    a figure of merit, resulting in dozens of tiny functions that
    caused control to jump all over the place (which made virtual
    memory systems thrash). And the end result wasn't that much
    more readable.

    The undisciplined use of GOTOs is bad, agreed. But the
    undisciplined use of function calls isn't a whole lot better.
    After all, a function call is just a GOTO paired with a
    "come from", so in the end it's all still spaghetti code -
    it's just that the "structured" code runs double strands.

    The "come from" IIRC is the key part here. If you use a function (and
    don't goto into its body, as that would undo the benefit here), you can
    analyze the function as a block with clearly defined flows and
    separately from the rest of the program.

    The criticism isn't about not putting everything into its own function,
    it's about how using functions and other flow control structures instead
    of e.g. gotos makes it easier to study and reason about these parts of
    the code.
    --
    Nuno Silva
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 01:27:31 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 23:18:44 GMT, Charlie Gibbs wrote:

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

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error
    recovery will invariably involve cleaning up those parts of the
    allocations which already succeeded. Gotos are no good for this;
    you need to exit levels of structure nesting one by one, disposing
    of allocations as you go.

    I know that a lot of CS types are going to stick pins into little
    dolls that look like me for saying this, but IMHO resource pointers,
    handles, etc. should be global.

    Surely any variable which is only used locally to a particular block
    should be declared local to that block. Why should resource pointers
    be any different?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 01:29:18 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every nested
    loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it works
    perfectly well.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 01:30:43 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 17:15:28 -0000 (UTC), Thomas Koenig wrote:

    But the attitude of not caring about speed can have grave results
    when the inefficiencies pile up.

    ThatrCOs not usually how code works, though. Execution time tends to
    follow a Pareto distribution -- spend your effort on the 10% of the
    code where 90% of the time is being spent, and that gives significant improvements without having to mess around with the other 90% of the
    code.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 01:35:49 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 15:20:29 -0500, Lynn McGuire wrote:

    Most of our convergence methods use Newton-Raphson, yes that Isaac
    Newton, to start, very quick to solve if it solves.

    Second-order convergence. That is, the number of digits of precision
    roughly doubles on every iteration -- when it works, that is.

    If that spirals out of control then we use the halving method, brute
    force and very slow. If that fails then we use an interpolation
    method, also very slow. If that fails (the flash is infeasible),
    then we report the failure to the user.

    Binary chop gives only first-order convergence, but it is guaranteed
    to converge if there is an answer. ThatrCOs why itrCOs always the last
    resort.

    No love for Runge-Kutta?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 20 19:06:44 2026
    From Newsgroup: comp.lang.fortran

    David Brown <david.brown@hesbynett.no> writes:
    [...]
    Multi-level break and continue (named loops) is on its way to C++, and
    will almost certainly be accepted sooner or later (since it is already
    in the draft of the next C standard):

    <https://www.open-std.org/jtc1/sc22/wg21/docs/papers/2025/p3568r0.html>

    Named break and continue are in the latest C2y draft:

    https://www.open-std.org/jtc1/sc22/wg14/www/docs/n3886.pdf

    They have been proposed for C++, but as far as I can tell have not
    (yet?) been incorporated into a draft C++ standard.

    https://github.com/cplusplus/draft

    [...]
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- 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 Wed Oct 21 16:11:28 2026
    From Newsgroup: comp.lang.fortran

    On 21/10/2026 06:20, Cryptoengineer wrote:
    On 10/20/2026 1:46 AM, Titus G wrote:
    On 20/10/2026 18:28, Thomas Koenig wrote:
    Scott Dorsey <kludge@panix.com> schrieb:
    Lynn McGuire-a <lynnmcguire5@gmail.com> wrote:
    One of the things that I am enjoying is that F2C gets rid of about 75% >>>>> of the Fortran Gotos.-a The remaining 25% Gotos usually make some
    sense.
    Ok, a little sense that any C or C++ programmer would have never
    used a
    goto there.

    It drives me up the wall when people use a goto to jump out of a do
    loop.
    The compiler is doing so much cleanup work that the programmer never
    sees.

    Again, care to give an example?

    I thought that what was called Structured Programming became an
    inviolable law when invented by whom I do not know but suspect that
    bugger for the bottle or even earlier.

    ITYM:

    Edgar Dijkstra: Go To Statement Considered Harmful

    https://homepages.cwi.nl/~storm/teaching/reader/Dijkstra68.pdf

    pt

    Not Aristotle but the date on that PDF was 1968.
    Initially we used to write spaghetti in Burroughs Assembler and machine language but after less than a year of my employment, newer larger
    hardware including a reliable hard disk was purchased by the commercial
    bureau and everything was rewritten using Structured Programming and
    COBOL which had a marvellously fast file indexing system and it became
    possible to read other programmers' programs with such advantages being
    great for the bureau but not so demanding and therefore rewarding for programmers.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 03:22:12 2026
    From Newsgroup: comp.lang.fortran

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

    On Tue, 20 Oct 2026 23:18:44 GMT, Charlie Gibbs wrote:

    I know that a lot of CS types are going to stick pins into little
    dolls that look like me for saying this, but IMHO resource pointers,
    handles, etc. should be global.

    Surely any variable which is only used locally to a particular block
    should be declared local to that block. Why should resource pointers
    be any different?

    Many resource pointers aren't local, though. Consider a program
    which loads a table from a file, then uses it for lookups while
    processing data in another file. You might decompose the program
    into a function that loads the table, and another that performs
    lookups. The main routine calls the table load routine, and opens
    the file to be processed. It then loops reading records, calling
    the lookup function each time. The table, dynamically allocated by
    the table load function, must remain allocated when the allocator
    exits, and must be available to the lookup function on each call;
    it cannot be local to either of those functions.
    --
    /~\ 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 John Levine@johnl@taugh.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 03:31:46 2026
    From Newsgroup: comp.lang.fortran

    According to William Hyde <wthyde1953@gmail.com>:
    Ah, I do love zombie comments, where someone has changed the code but
    left the comments as they were.

    i += 2; /* add 1 to i */
    --
    Regards,
    John Levine, johnl@taugh.com, Primary Perpetrator of "The Internet for Dummies",
    Please consider the environment before reading this e-mail. https://jl.ly
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ted@loft.tnolan.com (Ted Nolan@tednolan to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 04:31:00 2026
    From Newsgroup: comp.lang.fortran

    In article <11b9bn2$28tm$2@gal.iecc.com>, John Levine <johnl@taugh.com> wrote: >According to William Hyde <wthyde1953@gmail.com>:
    Ah, I do love zombie comments, where someone has changed the code but
    left the comments as they were.

    i += 2; /* add 1 to i */


    And then you find out it *does* add 1 to i. Somehow.
    --
    columbiaclosings.com
    What's not in Columbia anymore..
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 05:35:40 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 03:22:12 GMT, Charlie Gibbs wrote:

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

    On Tue, 20 Oct 2026 23:18:44 GMT, Charlie Gibbs wrote:

    I know that a lot of CS types are going to stick pins into little
    dolls that look like me for saying this, but IMHO resource
    pointers, handles, etc. should be global.

    Surely any variable which is only used locally to a particular
    block should be declared local to that block. Why should resource
    pointers be any different?

    Many resource pointers aren't local, though. Consider a program
    which loads a table from a file, then uses it for lookups while
    processing data in another file. You might decompose the program
    into a function that loads the table, and another that performs
    lookups. The main routine calls the table load routine, and opens
    the file to be processed. It then loops reading records, calling the
    lookup function each time. The table, dynamically allocated by the
    table load function, must remain allocated when the allocator exits,
    and must be available to the lookup function on each call; it cannot
    be local to either of those functions.

    This is why OO was invented. You instantiate a Table instance, and
    that loads the table contents. Call the lookup method on the instance
    as many times as you need. Then, when finished with the Table
    instance, dispose of it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 05:37:11 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 16:11:28 +1300, Titus G wrote:

    ... everything was rewritten using Structured Programming and COBOL
    which had a marvellously fast file indexing system and it became
    possible to read other programmers' programs with such advantages
    being great for the bureau but not so demanding and therefore
    rewarding for programmers.

    But then, business procedures moved away from ISAM files to embrace
    relational databases instead, and it turned out COBOL was a poor fit
    for managing SQL queries.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 07:42:30 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC)
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> wrote:
    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every nested
    loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it works >perfectly well.

    It may well work but it doesn't make it good. Its harder to follow - whereas
    a goto out of a deeply nested loops is blindingly obvious - and its less efficient.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 07:47:55 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 20:50:58 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 20/10/2026 19:24, boltar@battlestar.co.uk wrote:
    If C/C++ had multi level break and continue keywords goto would almost
    never be needed**. There's no reason they can't be added - along with a lot >of
    other useful but basic fatures (eg non POD switch, native concatting numbers >to
    std::string without calling to_string) - but I guess the committee are too >busy
    circle jerking with esoteric crap no one will ever use (eg concepts) to >bother.


    Multi-level break and continue (named loops) is on its way to C++, and
    will almost certainly be accepted sooner or later (since it is already
    in the draft of the next C standard):

    They should have been added 30 years ago.

    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking
    about and add nothing of actual value for the jobbing programmer trying to solve a problem.

    You might want to do some research before insulting the people who are >actually doing the work in driving languages forward.

    Driving it forward into a ditch. The language is already so needlessly complicated that students just swerve it for more user friendly ones, mainly Python. And Rust is already nudging C aside. If they ever add a decent object model to it then C++ will be next in the firing line.

    If I was starting out today in IT I wouldn't touch C++ with the proverbial barge pole.

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

    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow -
    whereas a goto out of a deeply nested loops is blindingly obvious -
    and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly
    obviousrCY ... ly wrong.

    What about the cleanup?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 08:05:02 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 07:55:39 -0000 (UTC)
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> wrote:
    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow -
    whereas a goto out of a deeply nested loops is blindingly obvious -
    and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly >obviousrCY ... ly wrong.

    Fine, well you stick with your gotos-are-bad religious doctrine based on something one guy said 50 years ago and the rest of us will carry on writing usable and easy to follow code.

    What about the cleanup?

    What about it? you think a flag test in a loop automagically fixes that?


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers,comp.lang.misc on Wed Oct 21 20:09:42 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/2026 7:18 AM, Charlie Gibbs wrote:
    On 2026-10-20, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Tue, 20 Oct 2026 19:04:55 GMT, Charlie Gibbs wrote:

    The undisciplined use of GOTOs is bad, agreed.

    Is there such a thing as a *disciplined* use of gotos?

    Yes, especially in COBOL or assembly language. For instance,
    a GOTO to the end of a function ensures any of its cleanup code
    gets executed, and fulfils a goal of structured proramming:
    each function has one exit point.

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error recovery
    will invariably involve cleaning up those parts of the allocations
    which already succeeded. Gotos are no good for this; you need to exit
    levels of structure nesting one by one, disposing of allocations as
    you go.

    I know that a lot of CS types are going to stick pins into little
    dolls that look like me for saying this, but IMHO resource pointers,
    handles, etc. should be global. Possible exceptions are resources
    that are going to be used solely by the current function - but even
    then, if that function calls another function that fails horribly,
    there's stuff that might not get cleaned up. That's why all my
    C programs contain a function quit_cleanup(char *errmsg), which
    de-allocates all resources and then exits (displaying "errmsg"
    if it isn't NULL). I can call that function anywhere, safe in
    the knowledge that by the time it finishes (it never returns),
    everything will have be freed.


    Side note: I chose not to comment on any of the other followups by the
    less experienced coders. I personally have no problem with your app-
    roach.

    That works for a single process, but once you start making libraries
    like Lua that can be loaded and then unloaded the rules change somewhat.

    SQLite3 can be used similarly.

    Though I doubt many people load either library dynamically, and then un-
    load; yet as far as I'm aware, both libraries support such usage.

    I added comp.lang.misc because I'm not aware of a Lua discussion group.

    Best wishes, and happy resource cleanup!
    --
    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 Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers,sci.math on Wed Oct 21 20:21:49 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/2026 9:30 AM, Lawrence DrCOOliveiro wrote:
    On Tue, 20 Oct 2026 17:15:28 -0000 (UTC), Thomas Koenig wrote:

    But the attitude of not caring about speed can have grave results
    when the inefficiencies pile up.

    ThatrCOs not usually how code works, though. Execution time tends to
    follow a Pareto distribution -- spend your effort on the 10% of the
    code where 90% of the time is being spent, and that gives significant improvements without having to mess around with the other 90% of the
    code.

    This is true of code. Yet, you can math yourself to a better solution.

    The /obvious/ example everyone here knows is sum of integers, as

    int sumint( int a ) {
    int value = 0 ;
    for ( int i = 1 ; i <= a ; i++ )
    value += i ;
    return value ;
    }

    whereas a mathematician might code it as

    int sumint( int a ) { return a * ( a + 1 ) / 2 ; }

    which is much faster for a large a.

    The point I'm making here is that if you myopically focus too much on
    the hot code, you might miss an obvious mathematical optimization.

    I added sci.math in case the wizards there want to add more obvious ex-
    amples I may not be aware of.


    Best wishes, and happy optimizations!
    --
    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 Thomas Koenig@tkoenig@netcologne.de to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 13:27:48 2026
    From Newsgroup: comp.lang.fortran

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:
    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow -
    whereas a goto out of a deeply nested loops is blindingly obvious -
    and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly obviousrCY ... ly wrong.

    What about the cleanup?

    What cleanup, exactly? We are talking Fortran, remember.
    --
    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 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 Wed Oct 21 07:37:04 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/26 20:31, John Levine wrote:
    According to William Hyde <wthyde1953@gmail.com>:
    Ah, I do love zombie comments, where someone has changed the code but
    left the comments as they were.

    i += 2; /* add 1 to i */


    LOL!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 07:41:06 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/26 01:05, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 07:55:39 -0000 (UTC)
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> wrote:
    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow -
    whereas a goto out of a deeply nested loops is blindingly obvious -
    and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly
    obviousrCY ... ly wrong.

    Fine, well you stick with your gotos-are-bad religious doctrine based on something one guy said 50 years ago and the rest of us will carry on writing usable and easy to follow code.

    What about the cleanup?

    What about it? you think a flag test in a loop automagically fixes that?

    I occasionally use GOTOs, but usually only after considering other alternatives. The flag test is the big red flag. If I have to keep
    testing a flag for several layers to get out of a loop, there has to be
    a better way.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Radey Shouman@shouman@comcast.net to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 10:41:49 2026
    From Newsgroup: comp.lang.fortran

    ted@loft.tnolan.com (Ted Nolan <tednolan>) writes:

    In article <11b9bn2$28tm$2@gal.iecc.com>, John Levine <johnl@taugh.com> wrote:
    According to William Hyde <wthyde1953@gmail.com>:
    Ah, I do love zombie comments, where someone has changed the code but >>>left the comments as they were.

    i += 2; /* add 1 to i */


    And then you find out it *does* add 1 to i. Somehow.

    Fixed point i with one fractional bit. Or something.
    --

    --- 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 Wed Oct 21 14:53:12 2026
    From Newsgroup: comp.lang.fortran

    Radey Shouman <shouman@comcast.net> writes:
    ted@loft.tnolan.com (Ted Nolan <tednolan>) writes:

    In article <11b9bn2$28tm$2@gal.iecc.com>, John Levine <johnl@taugh.com> wrote:
    According to William Hyde <wthyde1953@gmail.com>:
    Ah, I do love zombie comments, where someone has changed the code but >>>>left the comments as they were.

    i += 2; /* add 1 to i */


    And then you find out it *does* add 1 to i. Somehow.

    Fixed point i with one fractional bit. Or something.

    Or computing an index into an array of 16-bit entities
    in an array of bytes.
    --- 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 Wed Oct 21 11:06:19 2026
    From Newsgroup: comp.lang.fortran

    In article <11b9qna$pqb8$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking >about and add nothing of actual value for the jobbing programmer trying to >solve a problem.

    I kind of thought that way once. Then I worked with someone who decided
    to solve a problem that was NP-hard. I mentioned to him, "you know this is NP-hard, you'll never make it work for a reasonable number of elements"
    but he was convinced there was a solution. He worked on it for about a year before getting fired.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- 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 Wed Oct 21 23:10:26 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/2026 11:06 PM, Scott Dorsey wrote:
    In article <11b9qna$pqb8$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:
    David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking
    about and add nothing of actual value for the jobbing programmer trying to >> solve a problem.

    I kind of thought that way once. Then I worked with someone who decided
    to solve a problem that was NP-hard. I mentioned to him, "you know this is NP-hard, you'll never make it work for a reasonable number of elements"
    but he was convinced there was a solution. He worked on it for about a year before getting fired.
    --scott

    During that year, did he rewrite the code in Rust too?
    --
    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 drb@drb@ihatespam.msu.edu (Dennis Boone) to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 15:57:02 2026
    From Newsgroup: comp.lang.fortran

    i += 2; /* add 1 to i */

    And then you find out it *does* add 1 to i. Somehow.

    Very small values of 2.

    De
    --- 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 Wed Oct 21 17:57:35 2026
    From Newsgroup: comp.lang.fortran

    On 21/10/2026 09:47, boltar@battlestar.co.uk wrote:
    On Tue, 20 Oct 2026 20:50:58 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 20/10/2026 19:24, boltar@battlestar.co.uk wrote:
    If C/C++ had multi level break and continue keywords goto would almost
    never be needed**. There's no reason they can't be added - along with
    a lot
    of
    other useful but basic fatures (eg non POD switch, native concatting
    numbers
    to
    std::string without calling to_string) - but I guess the committee
    are too
    busy
    circle jerking with esoteric crap no one will ever use (eg concepts) to
    bother.


    Multi-level break and continue (named loops) is on its way to C++, and
    will almost certainly be accepted sooner or later (since it is already
    in the draft of the next C standard):

    They should have been added 30 years ago.


    That's your opinion, so I won't argue with it. I haven't felt the need
    of them myself, but I appreciate that some people expect to find them
    useful. They are now in the draft C2y, and implemented in gcc. It is
    likely (though not guaranteed) that they will make it to C++ too.

    Wishing they had been added 30 years ago does nothing - adding your
    voice of support in the C++ standards mailing lists, or asking gcc to
    add it as an extension in C++ might be more useful.

    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking about and add nothing of actual value for the jobbing programmer trying to solve a problem.

    I use them in my code. I am not alone in that.

    You are using them too, if you are using a relatively modern C++
    compiler - they are used in modern C++ standard library implementations.

    It's okay to consider them as "advanced", or something that "ordinary" programmers don't need - there's lots of stuff in C++ that most people
    don't need, but which exists so that it's easier to write efficient
    libraries that "ordinary" programmers /do/ use.


    You might want to do some research before insulting the people who are
    actually doing the work in driving languages forward.

    Driving it forward into a ditch. The language is already so needlessly complicated that students just swerve it for more user friendly ones,
    mainly
    Python. And Rust is already nudging C aside. If they ever add a decent object model to it then C++ will be next in the firing line.

    If I was starting out today in IT I wouldn't touch C++ with the proverbial barge pole.


    Ok. Again, that's your opinion.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From ted@loft.tnolan.com (Ted Nolan@tednolan to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 16:02:16 2026
    From Newsgroup: comp.lang.fortran

    In article <_Kicnccuc79TfUX3nZ2dnZfqnPadnZ2d@giganews.com>,
    Dennis Boone <drb@ihatespam.msu.edu> wrote:
    i += 2; /* add 1 to i */

    And then you find out it *does* add 1 to i. Somehow.

    Very small values of 2.

    De

    A co-worker actually tracked down such an issue. It turned out that
    in certain cases of misuse of indirection, you could assign new values
    to constants, such that '2' might have the value 1.
    --
    columbiaclosings.com
    What's not in Columbia anymore..
    --- 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 Wed Oct 21 12:29:05 2026
    From Newsgroup: comp.lang.fortran

    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    On 10/21/2026 11:06 PM, Scott Dorsey wrote:
    In article <11b9qna$pqb8$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>> David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking >>> about and add nothing of actual value for the jobbing programmer trying to >>> solve a problem.

    I kind of thought that way once. Then I worked with someone who decided
    to solve a problem that was NP-hard. I mentioned to him, "you know this is >> NP-hard, you'll never make it work for a reasonable number of elements"
    but he was convinced there was a solution. He worked on it for about a year >> before getting fired.

    During that year, did he rewrite the code in Rust too?

    If he'd have thought of that he probably could have milked another year out! --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 17:50:25 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 11:06:19 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:
    In article <11b9qna$pqb8$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking >>about and add nothing of actual value for the jobbing programmer trying to >>solve a problem.

    I kind of thought that way once. Then I worked with someone who decided
    to solve a problem that was NP-hard. I mentioned to him, "you know this is >NP-hard, you'll never make it work for a reasonable number of elements"
    but he was convinced there was a solution. He worked on it for about a year >before getting fired.

    I've no idea what point you're trying to make there.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 18:02:16 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 17:57:35 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 09:47, boltar@battlestar.co.uk wrote:
    They should have been added 30 years ago.


    That's your opinion, so I won't argue with it. I haven't felt the need
    of them myself, but I appreciate that some people expect to find them

    So you've never had to jump out of deeply nested loops? Are you the
    "hello world" guy?

    Wishing they had been added 30 years ago does nothing - adding your
    voice of support in the C++ standards mailing lists, or asking gcc to
    add it as an extension in C++ might be more useful.

    Its unlikely any compiler authors would add an extension that fundamentally changes the core flow of control without it being part of the standard.

    Yeah, on university CS courses. They're just more metaprogramming fucking
    about and add nothing of actual value for the jobbing programmer trying to >> solve a problem.

    I use them in my code. I am not alone in that.

    So fill us in on exactly what problem they solve because I've yet to see
    any use case that couldn't have been done with template specialisation, conditionals and typeid(). But I guess if you like yet more obtuse syntax
    that makes compilers even more bloated and bug prone then I'm sure they're
    a winner.

    It's okay to consider them as "advanced", or something that "ordinary" >programmers don't need - there's lots of stuff in C++ that most people
    don't need, but which exists so that it's easier to write efficient >libraries that "ordinary" programmers /do/ use.

    As I've already pointed out - there are far more mundane features that
    your average programmer WOULD use than the commitee can't be bothered to
    add probably because there's less peer kudos on that kind of thing than a
    load of highbrow bullshit that looks cool on a CS lecture whiteboard.

    Driving it forward into a ditch. The language is already so needlessly
    complicated that students just swerve it for more user friendly ones,
    mainly
    Python. And Rust is already nudging C aside. If they ever add a decent
    object model to it then C++ will be next in the firing line.

    If I was starting out today in IT I wouldn't touch C++ with the proverbial >> barge pole.


    Ok. Again, that's your opinion.

    Take a look around you. How many new startups are recruiting C++ devs?

    --- 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 Wed Oct 21 20:26:29 2026
    From Newsgroup: comp.lang.fortran

    On 21/10/2026 20:02, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 17:57:35 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 09:47, boltar@battlestar.co.uk wrote:
    They should have been added 30 years ago.


    That's your opinion, so I won't argue with it.-a I haven't felt the
    need of them myself, but I appreciate that some people expect to find
    them

    So you've never had to jump out of deeply nested loops? Are you the
    "hello world" guy?

    No, and no.

    There are plenty of ways to handle getting out of nested control
    structures. I can see why some people would like labelled loops and
    switches, and to be able to break or continue on those labels, but it
    simply hasn't been a problem for me. Alternatives like return from the function, or extra flag variables have been fine (the compiler turns the
    flag variables into jumps). It is quite possible that I have written
    code where I would have used multi-level breaks if they had been
    available at the time, but that's quite different from feeling they were missing from the language or that they would have been a much better
    solution.


    Wishing they had been added 30 years ago does nothing - adding your
    voice of support in the C++ standards mailing lists, or asking gcc to
    add it as an extension in C++ might be more useful.

    Its unlikely any compiler authors would add an extension that fundamentally changes the core flow of control without it being part of the standard.


    Don't exaggerate. It's a minor feature, with zero cost - it's a neater
    way to write "goto end_of_loop".

    Yeah, on university CS courses. They're just more metaprogramming
    fucking
    about and add nothing of actual value for the jobbing programmer
    trying to
    solve a problem.

    I use them in my code.-a I am not alone in that.

    So fill us in on exactly what problem they solve because I've yet to see
    any use case that couldn't have been done with template specialisation, conditionals and typeid(). But I guess if you like yet more obtuse syntax that makes compilers even more bloated and bug prone then I'm sure they're
    a winner.

    I haven't used them in any situation where they were /needed/, but I
    have used them where they make code neater and clearer. A lot of
    situations where you use concepts could be handled by a mess of
    enable_if's - but concepts are a better way to write the code.


    It's okay to consider them as "advanced", or something that "ordinary"
    programmers don't need - there's lots of stuff in C++ that most people
    don't need, but which exists so that it's easier to write efficient
    libraries that "ordinary" programmers /do/ use.

    As I've already pointed out - there are far more mundane features that
    your average programmer WOULD use than the commitee can't be bothered to
    add probably because there's less peer kudos on that kind of thing than a load of highbrow bullshit that looks cool on a CS lecture whiteboard.

    You are clearly have a lot of pent-up anger and frustration about
    something, since you haven't the faintest clue as to who the standards committee are, what they do, how they do it, and why they do it.
    (Here's a clue - most are C++ /users/, some are C++ compiler or standard library implementers. They are not academics.)


    Driving it forward into a ditch. The language is already so needlessly
    complicated that students just swerve it for more user friendly ones,
    mainly
    Python. And Rust is already nudging C aside. If they ever add a
    decent object model to it then C++ will be next in the firing line.

    If I was starting out today in IT I wouldn't touch C++ with the
    proverbial
    barge pole.


    Ok.-a Again, that's your opinion.

    Take a look around you. How many new startups are recruiting C++ devs?


    We see it all the time. Of course, different programming fields want different languages - C++ is suitable for some things, and less so for
    other things. There is no one language to fit all usage.

    There's plenty I don't like about C++ too. But I don't have some weird conspiracy theory about how it is being destroyed by some ivory tower academics that want C++ to be hard so that they can look smart, or
    whatever your delusions are.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 18:48:10 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 20:26:29 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:02, boltar@battlestar.co.uk wrote:
    Take a look around you. How many new startups are recruiting C++ devs?


    We see it all the time. Of course, different programming fields want >different languages - C++ is suitable for some things, and less so for
    other things. There is no one language to fit all usage.

    There's plenty I don't like about C++ too. But I don't have some weird >conspiracy theory about how it is being destroyed by some ivory tower >academics that want C++ to be hard so that they can look smart, or
    whatever your delusions are.

    Not sure why you think its conspiracy anything. I use the language on a
    daily basis and everytime a new version comes out I hope they've added something useful but since 2014 its been a law of diminishing returns.
    Plus there's unexplained omissions - eg threads have been part of the core language since 2011. Great, but what about processes? When do we get them? Sure, I could just use fork() but then I could also just use pthread_create() too.

    --- 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 Wed Oct 21 19:01:38 2026
    From Newsgroup: comp.lang.fortran

    In article <11bb1da$qfn9$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >On Wed, 21 Oct 2026 20:26:29 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:02, boltar@battlestar.co.uk wrote:
    Take a look around you. How many new startups are recruiting C++ devs?


    We see it all the time. Of course, different programming fields want >>different languages - C++ is suitable for some things, and less so for >>other things. There is no one language to fit all usage.

    There's plenty I don't like about C++ too. But I don't have some weird >>conspiracy theory about how it is being destroyed by some ivory tower >>academics that want C++ to be hard so that they can look smart, or >>whatever your delusions are.

    Not sure why you think its conspiracy anything. I use the language on a
    daily basis and everytime a new version comes out I hope they've added >something useful but since 2014 its been a law of diminishing returns.
    Plus there's unexplained omissions - eg threads have been part of the core >language since 2011. Great, but what about processes? When do we get them? >Sure, I could just use fork() but then I could also just use pthread_create() >too.

    One can implement a pretty reasonable threads library given the
    virtual machine model of standard C or C++. Processes? With
    their own address spaces, credentials, resource limits, IPC
    mechanisms, potentially running different programs, and so on?

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

    - 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 Wed Oct 21 12:17:48 2026
    From Newsgroup: comp.lang.fortran

    On 10/20/2026 8:31 PM, John Levine wrote:
    According to William Hyde <wthyde1953@gmail.com>:
    Ah, I do love zombie comments, where someone has changed the code but
    left the comments as they were.

    i += 2; /* add 1 to i */


    Oh how fun!
    --- 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 Wed Oct 21 14:12:47 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/26 10:50, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 11:06:19 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:
    In article <11b9qna$pqb8$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>> David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking >>> about and add nothing of actual value for the jobbing programmer trying to >>> solve a problem.

    I kind of thought that way once. Then I worked with someone who decided
    to solve a problem that was NP-hard. I mentioned to him, "you know this is >> NP-hard, you'll never make it work for a reasonable number of elements"
    but he was convinced there was a solution. He worked on it for about a year >> before getting fired.

    I've no idea what point you're trying to make there.

    He's trying to say that his university CS work paid off.

    I agree that the work for a CS degree is useful. If nothing else I
    understand more now.
    --- 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 Wed Oct 21 19:20:42 2026
    From Newsgroup: comp.lang.fortran

    In article <11bau11$29ugh$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >On Wed, 21 Oct 2026 11:06:19 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:
    In article <11b9qna$pqb8$1@dont-email.me>, <boltar@battlestar.co.uk> wrote: >>>David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking >>>about and add nothing of actual value for the jobbing programmer trying to >>>solve a problem.

    I kind of thought that way once. Then I worked with someone who decided
    to solve a problem that was NP-hard. I mentioned to him, "you know this is >>NP-hard, you'll never make it work for a reasonable number of elements"
    but he was convinced there was a solution. He worked on it for about a year >>before getting fired.

    I've no idea what point you're trying to make there.

    That knowing algorithm analysis has a valid use in the real world.
    --scott
    --
    "C'est un Nagra. C'est suisse, et tres, tres precis."
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 00:23:57 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 08:05:02 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 07:55:39 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    What about the cleanup?

    What about it? you think a flag test in a loop automagically fixes that?

    It needs to be done at each level before exiting to the outer level.

    I can show you some example code, if you like.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 00:24:48 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 13:27:48 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow
    - whereas a goto out of a deeply nested loops is blindingly
    obvious - and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly
    obviousrCY ... ly wrong.

    What about the cleanup?

    What cleanup, exactly? We are talking Fortran, remember.

    The principle applies to Fortran as it does to any language where you
    have to explicitly manage storage allocations.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 00:36:12 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 12:17:48 -0700, Chris M. Thomasson wrote:

    i += 2; /* add 1 to i */

    Oh how fun!

    ThatrCOs not the kind of comment I would have written, because I canrCOt
    see how it could ever have been useful. Perhaps something more explanatory, like (wild guess)

    i += 2; /* increment occurrences */

    and then the reader looks at the surrounding code to see what exactly
    are the rCLoccurrencesrCY being counted up, and that either confirms that
    2 is the right number to add, or it does not.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 00:37:08 2026
    From Newsgroup: comp.lang.fortran

    On 21 Oct 2026 16:02:16 GMT, Ted Nolan <tednolan> wrote:

    A co-worker actually tracked down such an issue. It turned out that
    in certain cases of misuse of indirection, you could assign new
    values to constants, such that '2' might have the value 1.

    Certain early Fortran implementations. CouldnrCOt happen in any other
    language ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 00:40:16 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 07:41:06 -0700, Peter Flass wrote:

    I occasionally use GOTOs, but usually only after considering other alternatives. The flag test is the big red flag. If I have to keep
    testing a flag for several layers to get out of a loop, there has to
    be a better way.

    If the flag indicates rCLan error has occurredrCY, then I think this is entirely reasonable.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 09:14:04 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 8:24 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 21 Oct 2026 13:27:48 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow
    - whereas a goto out of a deeply nested loops is blindingly
    obvious - and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly
    obviousrCY ... ly wrong.

    What about the cleanup?

    What cleanup, exactly? We are talking Fortran, remember.

    The principle applies to Fortran as it does to any language where you
    have to explicitly manage storage allocations.

    Never mind that when you use garbage collected languages, the finalizer
    can run at any point in the future, sometimes when you don't want it to.

    Such as too late.
    --
    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 Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran on Thu Oct 22 01:16:25 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Wed, 21 Oct 2026 13:27:48 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow
    - whereas a goto out of a deeply nested loops is blindingly
    obvious - and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly
    obviousrCY ... ly wrong.

    What about the cleanup?

    What cleanup, exactly? We are talking Fortran, remember.

    The principle applies to Fortran as it does to any language where you
    have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again,
    how *exactly* does using GOTO to break out of a Fortran 77 do
    loop require cleanup? With Fortran 90 (or newer version), even
    if one using some dynamic memory allocation, what is the cleanup
    you envision that is required if one break out of a do-loop with
    GOTO?

    PS: Both Thomas and I have made substantial code contributions to
    gfortran, so we must be missing something crucial.

    PPS: trimmed newsgroups to only c.l.f.
    --
    steve
    --- 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 Thu Oct 22 09:21:39 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 8:36 AM, Lawrence DrCOOliveiro wrote:
    On Wed, 21 Oct 2026 12:17:48 -0700, Chris M. Thomasson wrote:

    i += 2; /* add 1 to i */

    Oh how fun!

    ThatrCOs not the kind of comment I would have written, because I canrCOt
    see how it could ever have been useful. Perhaps something more explanatory, like (wild guess)

    i += 2; /* increment occurrences */

    and then the reader looks at the surrounding code to see what exactly
    are the rCLoccurrencesrCY being counted up, and that either confirms that
    2 is the right number to add, or it does not.

    That's just because you've stopped learning programming languages. You
    should take up Rust one of these days.

    Then you can find yourself writing comments like

    /* functions need to start with fn, */

    until you remember it. You see, functions don't start with fn in C, nor Fortran.

    And I personally don't understand why people are harping on that stu-
    dents shouldn't comment the obvious, because it isn't obvious to them
    because they haven't memorized the syntax yet.

    Of course, we /shouldn't/ have such code in production, but that's man-
    agerial problem. Some managers are fine with student written code, and
    vibe code. That's their problem. Especially when it stops working.
    --
    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 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 Thu Oct 22 09:51:46 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 2:48 AM, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 20:26:29 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:02, boltar@battlestar.co.uk wrote:
    Take a look around you. How many new startups are recruiting C++ devs?


    We see it all the time.-a Of course, different programming fields want
    different languages - C++ is suitable for some things, and less so for
    other things.-a There is no one language to fit all usage.

    There's plenty I don't like about C++ too.-a But I don't have some
    weird conspiracy theory about how it is being destroyed by some ivory
    tower academics that want C++ to be hard so that they can look smart,
    or whatever your delusions are.

    Not sure why you think its conspiracy anything. I use the language on a
    daily basis and everytime a new version comes out I hope they've added something useful but since 2014 its been a law of diminishing returns.
    Plus there's unexplained omissions - eg threads have been part of the core language since 2011. Great, but what about processes? When do we get them? Sure, I could just use fork() but then I could also just use pthread_create()
    too.

    There are what, three process models to wrap up? The Unix/Linux model,
    the N.T. model, and OpenVMS.

    If you need anything too different from those three, you can just fail
    with a compilation error on #include <process> or whatever.

    It isn't too hard to create a modern abstraction that does mostly the
    right thing.
    --
    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 02:00:29 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 01:16:25 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    The principle applies to Fortran as it does to any language where you
    have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again,
    how *exactly* does using GOTO to break out of a Fortran 77 do
    loop require cleanup?

    Read that again: rCLexplicitly manage storage allocationsrCY.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 02:17:59 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 02:00:29 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 01:16:25 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    The principle applies to Fortran as it does to any language where you
    have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again,
    how *exactly* does using GOTO to break out of a Fortran 77 do
    loop require cleanup?

    Read that again: rCLexplicitly manage storage allocationsrCY.

    Sure, what is the EXACT clean up that you envision? Here's some
    good old Fortran 77

    c234567
    INTEGER I(100)
    DO 10 N = 1, 100
    I(N) = I
    IF (N .EQ. 42) GOTO 11
    10 CONTINUE
    11 CONTINUE
    PRINT *, N
    END

    What is the clean-up? Your goal post seem to move.
    --
    steve
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 11:05:37 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 8:37 AM, Lawrence DrCOOliveiro wrote:
    On 21 Oct 2026 16:02:16 GMT, Ted Nolan <tednolan> wrote:

    A co-worker actually tracked down such an issue. It turned out that
    in certain cases of misuse of indirection, you could assign new
    values to constants, such that '2' might have the value 1.

    Certain early Fortran implementations. CouldnrCOt happen in any other language ...

    Did you never experiment with

    const int i = 3 ;
    int *p = &i ;
    *p = 1 ;

    in C, as a student?
    --
    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 Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 21 20:07:36 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/26 17:37, Lawrence DrCOOliveiro wrote:
    On 21 Oct 2026 16:02:16 GMT, Ted Nolan <tednolan> wrote:

    A co-worker actually tracked down such an issue. It turned out that
    in certain cases of misuse of indirection, you could assign new
    values to constants, such that '2' might have the value 1.

    Certain early Fortran implementations. CouldnrCOt happen in any other language ...

    Probably called a subroutine with constant 2 as an argument, which the subroutine modified. I don't think FORTRAN used dummy arguments or call-by-value.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 03:35:07 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 02:17:59 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 02:00:29 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 01:16:25 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    The principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again, how
    *exactly* does using GOTO to break out of a Fortran 77 do loop
    require cleanup?

    Read that again: rCLexplicitly manage storage allocationsrCY.

    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 03:46:30 2026
    From Newsgroup: comp.lang.fortran

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:
    On Wed, 21 Oct 2026 13:27:48 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to follow
    - whereas a goto out of a deeply nested loops is blindingly
    obvious - and its less efficient.

    The goto from the deep inner block to the outer one is rCLblindingly
    obviousrCY ... ly wrong.

    What about the cleanup?

    What cleanup, exactly? We are talking Fortran, remember.

    The principle applies to Fortran as it does to any language where you
    have to explicitly manage storage allocations.

    DO loops do not introduce scope in Fortran.
    --
    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 ted@loft.tnolan.com (Ted Nolan@tednolan to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 04:22:16 2026
    From Newsgroup: comp.lang.fortran

    In article <11bblrj$du80$5@dont-email.me>,
    Lawrence D Oliveiro <ldo@nz.invalid> wrote:
    On 21 Oct 2026 16:02:16 GMT, Ted Nolan <tednolan> wrote:

    A co-worker actually tracked down such an issue. It turned out that
    in certain cases of misuse of indirection, you could assign new
    values to constants, such that '2' might have the value 1.

    Certain early Fortran implementations. CouldnrCOt happen in any other >language ...

    Mumps.
    --
    columbiaclosings.com
    What's not in Columbia anymore..
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 04:33:04 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 03:35:07 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 02:17:59 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 02:00:29 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 01:16:25 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>
    The principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again, how
    *exactly* does using GOTO to break out of a Fortran 77 do loop
    require cleanup?

    Read that again: rCLexplicitly manage storage allocationsrCY.

    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    There isn't any "storage allocation" to cleanup. Of course,
    it would help if you actually define what you mean by "storage
    allocation". I gave you an example of Fortran 77 code where
    a GOTO jumps out of a do-loop. There is nothing to cleanup.

    So, please define "storage allocation" in the context of
    the Fortran language, and then define EXACTLY what you
    mean by cleanup.
    --
    steve
    --
    steve
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 04:50:10 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 04:33:04 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 03:35:07 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 02:17:59 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 02:00:29 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 01:16:25 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>
    The principle applies to Fortran as it does to any language
    where you have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again,
    how *exactly* does using GOTO to break out of a Fortran 77 do
    loop require cleanup?

    Read that again: rCLexplicitly manage storage allocationsrCY.

    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    There isn't any "storage allocation" to cleanup.

    Not in your example. Which is why it was irrelevant.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 04:51:11 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 03:46:30 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 13:27:48 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>
    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to
    follow - whereas a goto out of a deeply nested loops is
    blindingly obvious - and its less efficient.

    The goto from the deep inner block to the outer one is
    rCLblindingly obviousrCY ... ly wrong.

    What about the cleanup?

    What cleanup, exactly? We are talking Fortran, remember.

    The principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.

    DO loops do not introduce scope in Fortran.

    Nobody said anything about rCLscoperCY.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 04:56:06 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 04:50:10 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 04:33:04 -0000 (UTC), Steven G. Kargl wrote:


    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    There isn't any "storage allocation" to cleanup.

    Not in your example. Which is why it was irrelevant.

    Then give a Fortran 77 example that requires cleanup.
    You can't, can you?

    Using GOTO to jump out of do-loop in Fortran 77 does
    not lead to some mysterious "storage allocation" to
    cleanup.

    PS: a smart compiler would actually not generate code
    to execute the do-loop for the code in my example.
    --
    steve
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 14:22:01 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 11:07 AM, Peter Flass wrote:
    On 10/21/26 17:37, Lawrence DrCOOliveiro wrote:
    On 21 Oct 2026 16:02:16 GMT, Ted Nolan <tednolan> wrote:

    A co-worker actually tracked down such an issue. It turned out that
    in certain cases of misuse of indirection, you could assign new
    values to constants, such that '2' might have the value 1.

    Certain early Fortran implementations. CouldnrCOt happen in any other
    language ...

    Probably called a subroutine with constant 2 as an argument, which the subroutine modified. I don't think FORTRAN used dummy arguments or call- by-value.

    Reminds me of a bit of Elisp I wrote in XEmacs. Someone complained it
    modified -- or tried to modify? -- the literal array (?) I had when us-
    ing GNU Emacs. It's been a while. Anyway, I never experienced it as a
    bug, and I suppose there was a difference in implementation.

    So no, it's not just /early Fortran/.
    --
    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 Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 14:34:20 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 12:56 PM, Steven G. Kargl wrote:
    On Thu, 22 Oct 2026 04:50:10 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 04:33:04 -0000 (UTC), Steven G. Kargl wrote:


    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    There isn't any "storage allocation" to cleanup.

    Not in your example. Which is why it was irrelevant.

    Then give a Fortran 77 example that requires cleanup.
    You can't, can you?

    Using GOTO to jump out of do-loop in Fortran 77 does
    not lead to some mysterious "storage allocation" to
    cleanup.

    PS: a smart compiler would actually not generate code
    to execute the do-loop for the code in my example.


    Open Watcom Fortran 77 has /allocate/ and /deallocate/ according to a
    quick glance at the manual, but I have never used them.

    I guess the point is we don't want to allocate in a loop?
    --
    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 Thomas Koenig@tkoenig@netcologne.de to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 06:39:16 2026
    From Newsgroup: comp.lang.fortran

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:
    On Thu, 22 Oct 2026 03:46:30 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 13:27:48 -0000 (UTC), Thomas Koenig wrote:

    Lawrence DrCOOliveiro <ldo@nz.invalid> schrieb:

    On Wed, 21 Oct 2026 07:42:30 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 01:29:18 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>>
    On Tue, 20 Oct 2026 17:24:27 -0000 (UTC), boltar wrote:

    ** The setting a flag method which has to be checked in every
    nested loop test is just an [asinine] way to code.

    If you have to do cleanup at each level before exiting, then it
    works perfectly well.

    It may well work but it doesn't make it good. Its harder to
    follow - whereas a goto out of a deeply nested loops is
    blindingly obvious - and its less efficient.

    The goto from the deep inner block to the outer one is
    rCLblindingly obviousrCY ... ly wrong.

    What about the cleanup?

    What cleanup, exactly? We are talking Fortran, remember.

    The principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.

    DO loops do not introduce scope in Fortran.

    Nobody said anything about rCLscoperCY.

    Somebody who knows the first thing about Fortran, which you
    clearly don't, might have realized that scope is the only
    way to mandate storage allocation/deallocation in Fortran.
    --
    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 Thu Oct 22 09:20:53 2026
    From Newsgroup: comp.lang.fortran

    On 21/10/2026 20:48, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 20:26:29 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:02, boltar@battlestar.co.uk wrote:
    Take a look around you. How many new startups are recruiting C++ devs?


    We see it all the time.-a Of course, different programming fields want
    different languages - C++ is suitable for some things, and less so for
    other things.-a There is no one language to fit all usage.

    There's plenty I don't like about C++ too.-a But I don't have some
    weird conspiracy theory about how it is being destroyed by some ivory
    tower academics that want C++ to be hard so that they can look smart,
    or whatever your delusions are.

    Not sure why you think its conspiracy anything.

    When a group of people or entities are working together with a secret
    agenda that is opposing (or at least independent of) their claimed open agenda, that's a conspiracy. The phrase "conspiracy theory" is usually applied when someone believes their is a conspiracy without suitable
    evidence or justification.

    Thus your opinion of the C++ standards committee's work and motivation
    is a conspiracy theory. It's not a remotely dangerous one - but it is
    still a daft one.

    This is very different from simply saying that you haven't found much
    use for the features added to the C++ language or library in recent
    years, or that you find the new features more complex than they are
    worth, or that you are disappointed that features you hoped for were not added. That would be an entirely legitimate opinion based on personal preferences, experiences and needs.

    I use the language on a
    daily basis and everytime a new version comes out I hope they've added something useful but since 2014 its been a law of diminishing returns.

    That is inevitable, and applies to all languages. Big, established
    languages already cover most needs of most users. /No one/ uses all the features of C++, or Python, or Java. No one is interested in /all/ the
    new features they gain. That does not mean they can't evolve and
    improve. If I look at Wikipedia's list of what is new in C++20, there
    are about 20 language changes and 15 major library changes. I use
    perhaps 4 or 5 of these, and am somewhat interested in a couple more.
    For C++23, the list of changes is much longer, but there is only one
    that made me change to -std=gnu++23. But for a much larger proportion
    of the changes, I can understand how they could be useful to other people.

    Plus there's unexplained omissions - eg threads have been part of the core language since 2011. Great, but what about processes? When do we get them? Sure, I could just use fork() but then I could also just use pthread_create()
    too.

    Equally, no language can support all the features that users might want.

    For the particular case of why C++ supports threads but not processes,
    the answer should be obvious.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 07:31:48 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 14:34:20 +0800, Johann 'Myrkraverk' Oskarsson wrote:

    On 10/22/2026 12:56 PM, Steven G. Kargl wrote:
    On Thu, 22 Oct 2026 04:50:10 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 04:33:04 -0000 (UTC), Steven G. Kargl wrote:


    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    There isn't any "storage allocation" to cleanup.

    Not in your example. Which is why it was irrelevant.

    Then give a Fortran 77 example that requires cleanup.
    You can't, can you?

    Using GOTO to jump out of do-loop in Fortran 77 does
    not lead to some mysterious "storage allocation" to
    cleanup.

    PS: a smart compiler would actually not generate code
    to execute the do-loop for the code in my example.


    Open Watcom Fortran 77 has /allocate/ and /deallocate/ according to a
    quick glance at the manual, but I have never used them.

    Dynamic memory management via allocate/deallocate was introduce
    in Fortran 90. Open Watcom Fortran 77 may have added those as
    an extension. The Fortran 77 standard does have a dynamic memory
    feature. But, this seems irrelevant to Lawrence, who has coined
    the term "storage allocation", which is not Fortran terminology.
    We are now waiting for a definition for this term.

    I guess the point is we don't want to allocate in a loop?

    I allocate memory in do-loops all time. It would be a significant pessimization to write something like

    integer, allocatable :: i(:)
    i = [0] ! A 1-element array.
    do j = 1, 9
    i = [i,j] ! Re-allocate i on assignment
    end do
    10 print *, i
    end

    Note, there is no clean up of 'storage allocation' when the
    loop terminates. The Fortran standard does not mandate when
    memory that may have been freed during the re-allocation is
    actually garbaged collected. The program could return memory
    to the system during the re-allocation or when the program
    terminates.
    --
    steve

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 16:40:21 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 3:31 PM, Steven G. Kargl wrote:
    On Thu, 22 Oct 2026 14:34:20 +0800, Johann 'Myrkraverk' Oskarsson wrote:

    On 10/22/2026 12:56 PM, Steven G. Kargl wrote:
    On Thu, 22 Oct 2026 04:50:10 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 04:33:04 -0000 (UTC), Steven G. Kargl wrote:


    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    There isn't any "storage allocation" to cleanup.

    Not in your example. Which is why it was irrelevant.

    Then give a Fortran 77 example that requires cleanup.
    You can't, can you?

    Using GOTO to jump out of do-loop in Fortran 77 does
    not lead to some mysterious "storage allocation" to
    cleanup.

    PS: a smart compiler would actually not generate code
    to execute the do-loop for the code in my example.


    Open Watcom Fortran 77 has /allocate/ and /deallocate/ according to a
    quick glance at the manual, but I have never used them.

    Dynamic memory management via allocate/deallocate was introduce
    in Fortran 90. Open Watcom Fortran 77 may have added those as
    an extension. The Fortran 77 standard does have a dynamic memory
    feature. But, this seems irrelevant to Lawrence, who has coined
    the term "storage allocation", which is not Fortran terminology.
    We are now waiting for a definition for this term.

    Lawrence, in my experience, pretends to be a much more experienced pro-
    grammer than he is. In my opinion, he's just a Python influencer.

    So we keep waiting.


    I guess the point is we don't want to allocate in a loop?

    I allocate memory in do-loops all time. It would be a significant pessimization to write something like

    integer, allocatable :: i(:)
    i = [0] ! A 1-element array.
    do j = 1, 9
    i = [i,j] ! Re-allocate i on assignment
    end do
    10 print *, i
    end

    Note, there is no clean up of 'storage allocation' when the
    loop terminates. The Fortran standard does not mandate when
    memory that may have been freed during the re-allocation is
    actually garbaged collected. The program could return memory
    to the system during the re-allocation or when the program
    terminates.


    Thanks. I admit some lacking in understanding of Fortran, 77 and other-
    wise, so I'll read better upon this stuff before I start to use it.

    In other news, I have no problem understanding the Fortran 77 code snip-
    pets in my /Digital Image Processing/ (1993) by Gonzales and Woods.
    Sometimes code literacy is sufficient.

    Best wishes, and happy Fortran!
    --
    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 Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 07:26:21 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/26 20:35, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 02:17:59 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 02:00:29 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 01:16:25 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>
    The principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again, how
    *exactly* does using GOTO to break out of a Fortran 77 do loop
    require cleanup?

    Read that again: rCLexplicitly manage storage allocationsrCY.

    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    That's why I try to use PL/I AUTOMATIC (stack) storage and not allocate
    a lot of stuff. You need to have a disciplined approach if you allocate
    random stuff here and there.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 14:50:24 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 14:51:31 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 21 Oct 2026 14:12:47 -0700
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/21/26 10:50, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 11:06:19 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:
    In article <11b9qna$pqb8$1@dont-email.me>, <boltar@battlestar.co.uk> wrote:

    David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming fucking >>>> about and add nothing of actual value for the jobbing programmer trying to >>>> solve a problem.

    I kind of thought that way once. Then I worked with someone who decided >>> to solve a problem that was NP-hard. I mentioned to him, "you know this is >>> NP-hard, you'll never make it work for a reasonable number of elements"
    but he was convinced there was a solution. He worked on it for about a year

    before getting fired.

    I've no idea what point you're trying to make there.

    He's trying to say that his university CS work paid off.

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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 14:53:36 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 00:23:57 -0000 (UTC)
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> wrote:
    On Wed, 21 Oct 2026 08:05:02 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 07:55:39 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    What about the cleanup?

    What about it? you think a flag test in a loop automagically fixes that?

    It needs to be done at each level before exiting to the outer level.

    That depends on what you've done doesn't it. If you're stupid enough to
    use a raw new or malloc() then thats your lookout. The rest of us will use stack objects, shared_ptr or similar.

    I can show you some example code, if you like.

    No thanks, I'd rather not get any bad habits.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@battlestar.co.uk to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 14:54:21 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 09:51:46 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    On 10/22/2026 2:48 AM, boltar@battlestar.co.uk wrote:
    Not sure why you think its conspiracy anything. I use the language on a
    daily basis and everytime a new version comes out I hope they've added
    something useful but since 2014 its been a law of diminishing returns.
    Plus there's unexplained omissions - eg threads have been part of the core >> language since 2011. Great, but what about processes? When do we get them? >> Sure, I could just use fork() but then I could also just use
    pthread_create()
    too.

    There are what, three process models to wrap up? The Unix/Linux model,
    the N.T. model, and OpenVMS.

    If you need anything too different from those three, you can just fail
    with a compilation error on #include <process> or whatever.

    It isn't too hard to create a modern abstraction that does mostly the
    right thing.

    Exactly.

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

    On Thu, 22 Oct 2026 09:20:53 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:48, boltar@battlestar.co.uk wrote:
    Not sure why you think its conspiracy anything.

    When a group of people or entities are working together with a secret
    agenda that is opposing (or at least independent of) their claimed open >agenda, that's a conspiracy. The phrase "conspiracy theory" is usually >applied when someone believes their is a conspiracy without suitable >evidence or justification.

    Thus your opinion of the C++ standards committee's work and motivation
    is a conspiracy theory. It's not a remotely dangerous one - but it is
    still a daft one.

    Only in your mind is it a conspirary theory. You seem unable to tell the difference between a criticism of being out of touch and a conspiracy.
    You'd probably do well in Maga.

    languages already cover most needs of most users. /No one/ uses all the >features of C++, or Python, or Java. No one is interested in /all/ the
    new features they gain. That does not mean they can't evolve and
    improve. If I look at Wikipedia's list of what is new in C++20, there
    are about 20 language changes and 15 major library changes. I use
    perhaps 4 or 5 of these, and am somewhat interested in a couple more.
    For C++23, the list of changes is much longer, but there is only one
    that made me change to -std=gnu++23. But for a much larger proportion
    of the changes, I can understand how they could be useful to other people.

    Constantly adding very nich features to a language is not a sign of the language evolving, its a sign of it running out of steam.

    Plus there's unexplained omissions - eg threads have been part of the core >> language since 2011. Great, but what about processes? When do we get them? >> Sure, I could just use fork() but then I could also just use
    pthread_create()
    too.

    Equally, no language can support all the features that users might want.

    Useful core basic features should be done before any niche features.

    For the particular case of why C++ supports threads but not processes,
    the answer should be obvious.

    No, its not obvious because there is no good reason why it couldn't provide
    the facility. Whats that you say? Not all platforms support multi process? Newsflash - not all platforms support threading, eg PICs. HTH.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From James Kuyper@jameskuyper@alumni.caltech.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 11:18:03 2026
    From Newsgroup: comp.lang.fortran

    On 2026-10-22 00:50, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 04:33:04 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 03:35:07 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 02:17:59 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 02:00:29 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>
    On Thu, 22 Oct 2026 01:16:25 -0000 (UTC), Steven G. Kargl wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>>
    The principle applies to Fortran as it does to any language
    where you have to explicitly manage storage allocations.

    Fortran 77 does not have dynamic memory allocation. So, again,
    how *exactly* does using GOTO to break out of a Fortran 77 do
    loop require cleanup?

    Read that again: rCLexplicitly manage storage allocationsrCY.

    Sure, what is the EXACT clean up that you envision?

    rCLStorage allocationsrCY.

    There isn't any "storage allocation" to cleanup.

    Not in your example. Which is why it was irrelevant.

    So, why can't you provide an example of storage allocation, where
    cleanup is relevant, so that using a GOTO would be problematic. That way
    we could have some idea what you're talking about.
    This discussion is currently cross-posted to four newsgroups, only one
    of which is specifically about Fortran. You can reasonably assume that
    many people here are unfamiliar with Fortran. I've earned money writing Fortran, but very little, and most of it was a decades ago. I personally
    have no idea what you're referring to.
    --- 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 22 16:02:35 2026
    From Newsgroup: comp.lang.fortran

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

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

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

    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.

    A virtual machine (vmware, kvm, xen, et alia) is an orange.

    assert(apples != oranges);

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

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

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

    There have been, in the past, threading models that support both
    hardware threads and pure software threads (e.g. SVR4.2ES/MP)
    in a single application. It was not a joke then, it's not a joke now.

    --- 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 Thu Oct 22 12:19:49 2026
    From Newsgroup: comp.lang.fortran

    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.

    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.

    If you just want a job, getting one of these degrees is not for you. It's
    not there for that.
    --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 Thu Oct 22 16:22:30 2026
    From Newsgroup: comp.lang.fortran

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

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

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

    Scott addressed this. I guess we can be all pedantic and should
    properly call it the "abstract machine", but I assumed most
    people here would understand that THE "abstract machine" defined
    in the C standard is AN INSTANCE of using a "virtual machine
    *model*" applied to a specific task: defining the behavior of C.
    That is qualitatively different than a "virtual machine" that is
    virtualizing a CPU, real or theoretical.

    On well, you know what they say about assuming....

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

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

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

    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.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 19:05:16 2026
    From Newsgroup: comp.lang.fortran

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

    On Wed, 21 Oct 2026 08:05:02 -0000 (UTC), boltar wrote:

    On Wed, 21 Oct 2026 07:55:39 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    What about the cleanup?

    What about it? you think a flag test in a loop automagically fixes that?

    It needs to be done at each level before exiting to the outer level.

    I can show you some example code, if you like.

    Maybe the flag needs to be global. <g,d&r>
    --
    /~\ 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 Charlie Gibbs@cgibbs@kltpzyxm.invalid to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 19:05:17 2026
    From Newsgroup: comp.lang.fortran

    On 2026-10-22, boltar@battlestar.co.uk <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.

    I was in the CS program - but I found a part-time programming
    job and found that I preferred the Real World, so I dropped out
    and turned that part-time job into a full-time career.

    I wasn't much into staring at battleships either. ;-)
    --
    /~\ 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 Thu Oct 22 22:44:12 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 14:54:21 -0000 (UTC)
    boltar@battlestar.co.uk wrote:

    On Thu, 22 Oct 2026 09:51:46 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:
    On 10/22/2026 2:48 AM, boltar@battlestar.co.uk wrote:
    Not sure why you think its conspiracy anything. I use the language
    on a daily basis and everytime a new version comes out I hope
    they've added something useful but since 2014 its been a law of
    diminishing returns. Plus there's unexplained omissions - eg
    threads have been part of the core language since 2011. Great, but
    what about processes? When do we get them? Sure, I could just use
    fork() but then I could also just use pthread_create()
    too.

    There are what, three process models to wrap up? The Unix/Linux
    model, the N.T. model, and OpenVMS.

    If you need anything too different from those three, you can just
    fail with a compilation error on #include <process> or whatever.

    It isn't too hard to create a modern abstraction that does mostly the
    right thing.

    Exactly.


    C++ (and C) standard library provides minimal and limited support
    for processes:
    https://en.cppreference.com/cpp/utility/program/system

    I suppose that you want more.
    Of course it is possible to standardize either https://www.man7.org/linux/man-pages/man3/posix_spawn.3.html
    or
    https://en.wikibooks.org/wiki/C_programming/POSIX_reference/spawn
    or something in the middle.

    May be, it would be even a little useful.
    But if C++ committee tasked with that I am afraid that they will end up
    with unnecessary complicated stuff, like they did with time
    measurements.
    If C committee does it, I'd expect better results. But then, I don't
    expect that C committee will be bothered.









    --- 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 22 22:48:29 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 14:51:31 -0000 (UTC)
    boltar@battlestar.co.uk wrote:

    On Wed, 21 Oct 2026 14:12:47 -0700
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/21/26 10:50, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 11:06:19 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:
    In article <11b9qna$pqb8$1@dont-email.me>,
    <boltar@battlestar.co.uk> wrote:

    David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more
    metaprogramming fucking about and add nothing of actual value
    for the jobbing programmer trying to solve a problem.

    I kind of thought that way once. Then I worked with someone who
    decided to solve a problem that was NP-hard. I mentioned to him,
    "you know this is NP-hard, you'll never make it work for a
    reasonable number of elements" but he was convinced there was a
    solution. He worked on it for about a year

    before getting fired.

    I've no idea what point you're trying to make there.

    He's trying to say that his university CS work paid off.

    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?

    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.



    --- 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 Fri Oct 23 03:52:03 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 10:58 PM, boltar@battlestar.co.uk wrote:
    On Thu, 22 Oct 2026 09:20:53 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:48, boltar@battlestar.co.uk wrote:
    Not sure why you think its conspiracy anything.

    When a group of people or entities are working together with a secret
    agenda that is opposing (or at least independent of) their claimed
    open agenda, that's a conspiracy.-a The phrase "conspiracy theory" is
    usually applied when someone believes their is a conspiracy without
    suitable evidence or justification.

    Thus your opinion of the C++ standards committee's work and motivation
    is a conspiracy theory.-a It's not a remotely dangerous one - but it is
    still a daft one.

    Only in your mind is it a conspirary theory. You seem unable to tell the difference between a criticism of being out of touch and a conspiracy.
    You'd probably do well in Maga.

    languages already cover most needs of most users.-a /No one/ uses all
    the features of C++, or Python, or Java.-a No one is interested in /
    all/ the new features they gain.-a That does not mean they can't evolve
    and improve.-a If I look at Wikipedia's list of what is new in C++20,
    there are about 20 language changes and 15 major library changes.-a I
    use perhaps 4 or 5 of these, and am somewhat interested in a couple
    more. For C++23, the list of changes is much longer, but there is only
    one that made me change to -std=gnu++23.-a But for a much larger
    proportion of the changes, I can understand how they could be useful
    to other people.

    Constantly adding very nich features to a language is not a sign of the language evolving, its a sign of it running out of steam.

    Plus there's unexplained omissions - eg threads have been part of the
    core
    language since 2011. Great, but what about processes? When do we get
    them?
    Sure, I could just use fork() but then I could also just use
    pthread_create()
    too.

    Equally, no language can support all the features that users might want.

    Useful core basic features should be done before any niche features.

    For the particular case of why C++ supports threads but not processes,
    the answer should be obvious.

    No, its not obvious because there is no good reason why it couldn't provide the facility. Whats that you say? Not all platforms support multi process? Newsflash - not all platforms support threading, eg PICs. HTH.

    Dear boltar,

    I am delighted you've met some of the trolls of comp.lang.c; well, I
    guess comp.lang.c++ in your case.

    They pretend to have a lot to say, but we both know they don't.

    So take it easy, think of good flames, and reinterpret_cast< flame >
    ( with.precision ) ; and enjoy.

    Or if not, stop replying, and move on with your life. They won't stop.


    Best wishes, and happy C++!
    --
    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 Thu Oct 22 16:25:58 2026
    From Newsgroup: comp.lang.fortran

    On 2026-10-22 12:02, Scott Lurndal wrote:
    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.

    And could you tell me where I might find that description? The word
    "virtual" appears in the C standard only when describing one of the
    committee meetings. No two of words in "virtual machine model" appear consecutively anywhere in the C++ standard.
    --- 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 Thu Oct 22 16:27:50 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 10:51 AM, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 14:12:47 -0700
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/21/26 10:50, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 11:06:19 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:
    In article <11b9qna$pqb8$1@dont-email.me>,
    <boltar@battlestar.co.uk> wrote:

    David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming
    fucking
    about and add nothing of actual value for the jobbing programmer
    trying to
    solve a problem.

    I kind of thought that way once.-a Then I worked with someone who
    decided
    to solve a problem that was NP-hard.-a I mentioned to him, "you know
    this is
    NP-hard, you'll never make it work for a reasonable number of elements" >>>> but he was convinced there was a solution.-a He worked on it for
    about a year

    before getting fired.

    I've no idea what point you're trying to make there.

    He's trying to say that his university CS work paid off.

    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. 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 new. When I started programming professionally, CS degrees were
    rare as hen's teeth. At the Wall Street bank where I worked, we did get
    one employee with a CS degree, of which he was extremely proud.

    He lasted 6 months before being laid off.

    pt
    --- 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 Thu Oct 22 15:36:49 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 9:51 AM, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 14:12:47 -0700
    Peter Flass <Peter@Iron-Spring.com> wrote:
    On 10/21/26 10:50, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 11:06:19 -0400 (EDT)
    kludge@panix.com (Scott Dorsey) wrote:
    In article <11b9qna$pqb8$1@dont-email.me>,
    <boltar@battlestar.co.uk> wrote:

    David Brown <david.brown@hesbynett.no> wrote:
    And people /do/ use concepts, even if you do not.

    Yeah, on university CS courses. They're just more metaprogramming
    fucking
    about and add nothing of actual value for the jobbing programmer
    trying to
    solve a problem.

    I kind of thought that way once.-a Then I worked with someone who
    decided
    to solve a problem that was NP-hard.-a I mentioned to him, "you know
    this is
    NP-hard, you'll never make it work for a reasonable number of elements" >>>> but he was convinced there was a solution.-a He worked on it for
    about a year

    before getting fired.

    I've no idea what point you're trying to make there.

    He's trying to say that his university CS work paid off.

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

    My bachelor degree is in Mechanical Engineering from TAMU. I started
    working for my father's engineering software company writing Fortran in
    1975 when I was 14. I tested out of the Fortran courses at TAMU and did
    take a course in IBM 370 assembly language programming to see what
    assembly language was about. Of course I never took programming courses
    in Algorithms or Compiler Design.

    Lynn

    --- 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 Thu Oct 22 15:41:15 2026
    From Newsgroup: comp.lang.fortran

    On 10/21/2026 8:51 PM, Johann 'Myrkraverk' Oskarsson wrote:
    On 10/22/2026 2:48 AM, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 20:26:29 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:02, boltar@battlestar.co.uk wrote:
    Take a look around you. How many new startups are recruiting C++ devs? >>>>

    We see it all the time.-a Of course, different programming fields want
    different languages - C++ is suitable for some things, and less so
    for other things.-a There is no one language to fit all usage.

    There's plenty I don't like about C++ too.-a But I don't have some
    weird conspiracy theory about how it is being destroyed by some ivory
    tower academics that want C++ to be hard so that they can look smart,
    or whatever your delusions are.

    Not sure why you think its conspiracy anything. I use the language on a
    daily basis and everytime a new version comes out I hope they've added
    something useful but since 2014 its been a law of diminishing returns.
    Plus there's unexplained omissions - eg threads have been part of the
    core
    language since 2011. Great, but what about processes? When do we get
    them?
    Sure, I could just use fork() but then I could also just use
    pthread_create()
    too.

    There are what, three process models to wrap up?-a The Unix/Linux model,
    the N.T. model, and OpenVMS.

    If you need anything too different from those three, you can just fail
    with a compilation error on #include <process> or whatever.

    It isn't too hard to create a modern abstraction that does mostly the
    right thing.

    Now add the User Interface systems for the operating systems. And the
    current Apple system does not even have a C++ user interface.

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    Lynn

    --- 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 Thu Oct 22 22:01:53 2026
    From Newsgroup: comp.lang.fortran

    In article <11bdrgn$16ne1$1@dont-email.me>,
    James Kuyper <jameskuyper@alumni.caltech.edu> 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.

    And could you tell me where I might find that description? The word
    "virtual" appears in the C standard only when describing one of the
    committee meetings. No two of words in "virtual machine model" appear >consecutively anywhere in the C++ standard.

    Addressed in an earlier post: the term of art is in the actual
    text of the standard is, "abstract machine." But that is an
    example of using a model of a virtual machine to describe
    something; in this case, the semantics of executing a C program.

    It's a more abstract reading, sure, but again I'd have thought
    it was intuitive.

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 16:54:12 2026
    From Newsgroup: comp.lang.fortran

    Thomas Koenig <tkoenig@netcologne.de> writes:
    [...]
    Somebody who knows the first thing about Fortran, which you
    clearly don't, might have realized that scope is the only
    way to mandate storage allocation/deallocation in Fortran.

    Is that true in more recent versions of Fortran?

    A quick web search indicates that Fortran 90 added "allocate"
    and "deallocate". If I understand correctly, you might have an
    "allocate" inside a DO loop, and breaking out of the loop could
    bypass the corresponding "deallocate".

    LDO doesn't write coherently enough to know whether that's what
    he's talking about.

    Disclaimer: I do know the first thing about Fortran, and probably
    the second, but not the third and fourth. Ironically, I happen
    to know the seventeenth, but I'll never tell.
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++ on Fri Oct 23 01:57:42 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 16:54:12 -0700, Keith Thompson wrote:

    Thomas Koenig <tkoenig@netcologne.de> writes:
    [...]
    Somebody who knows the first thing about Fortran, which you
    clearly don't, might have realized that scope is the only
    way to mandate storage allocation/deallocation in Fortran.

    Is that true in more recent versions of Fortran?

    A quick web search indicates that Fortran 90 added "allocate"
    and "deallocate". If I understand correctly, you might have an
    "allocate" inside a DO loop, and breaking out of the loop could
    bypass the corresponding "deallocate".


    As Thomas indicated, it depends on scope. A function is
    a scoping unit. For this simple function,

    function foo(n)
    integer foo
    integer, intent(in) :: n
    integer, allocatable :: i(:)
    allocate(i(n))
    do j = 1, n
    i(j) = j
    end do
    foo = sum(i)
    end function

    'i' is a local variable, which is allocated to have 'n' elements.
    When the function returns, Fortran will automatically deallocate
    'i'. A do-loop is not a scoping unit, so there is no deallocation
    when a loop ends. Here's a function that has an allocate in
    the do-loop

    function foo(n)
    integer foo
    integer, intent(in) :: n
    integer, allocatable :: i(:)
    do j = 1, n
    allocate(i(j)) ! allocate i to have j elements
    i = j ! set all elements to j
    print *, sum(i)
    if (j == n / 2) exit
    deallocate(i) ! free for next loop iteration
    end do
    foo = sum(i) ! On exit from loop, i is still allocated
    end function

    If the if-condition is false, the user must deallocate 'i'
    for the next iteration of the loop. Fortran does not have a
    realloc() function. When the loop is exited on a true
    condition, 'i' is still allocated and can be referenced in
    the last assignment statement to foo. Finally, when the
    function returns, 'i' is deallocated as its a local variable.

    It can be a bit more complicated with some newer Fortran
    features such as ASSOCIATE and BLOCK constructs that define
    scoping units with a scoping unit. But, in general a local
    entity that is allocated with a scoping unit will be deallocated
    when the scoping unit goes out-of-scope.

    PS: trimmed the rust and folklore newsgroups as this is
    irrelevant to those.
    --
    steve
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 03:19:13 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach if
    you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 03:21:49 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.

    I gather thererCOs been a proposal thatrCOs been kicking around for some
    years, to adopt something based on Cairo
    <https://www.cairographics.org/>.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 03:33:44 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 11:18:03 -0400, James Kuyper wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    The principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.

    So, why can't you provide an example of storage allocation, where
    cleanup is relevant, so that using a GOTO would be problematic. That
    way we could have some idea what you're talking about.

    The technique I use is based on a form of structured programming
    called a rCLNassi-Shneiderman diagramrCY. The overall structure looks like

    ... initialize object pointer to NULL ...
    do /*once*/
    {
    ... possible other stuff ...
    ... allocate object pointer ...
    if (error occurred)
    break;
    ... possible other stuff using object pointer ...
    }
    while (false);
    ... call free(3) (or equivalent) on object pointer ...

    So you can see there is no way out of the inner block without passing
    through the dispose call. Using gotos would contribute nothing except
    make it harder to assure yourself of the simplicity of the control
    flow.

    Looks deceptively simple. But the same technique can scale up to quite
    complex cases. Which we can get to, if you want.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++ on Fri Oct 23 04:10:39 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 03:33:44 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 11:18:03 -0400, James Kuyper wrote:

    On Thu, 22 Oct 2026 00:24:48 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    The principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.

    So, why can't you provide an example of storage allocation, where
    cleanup is relevant, so that using a GOTO would be problematic. That
    way we could have some idea what you're talking about.

    The technique I use is based on a form of structured programming
    called a rCLNassi-Shneiderman diagramrCY. The overall structure looks like

    ... initialize object pointer to NULL ...
    do /*once*/
    {
    ... possible other stuff ...
    ... allocate object pointer ...
    if (error occurred)
    break;
    goto error;
    ... possible other stuff using object pointer ...
    }
    while (false);
    error:
    ... call free(3) (or equivalent) on object pointer ...

    So you can see there is no way out of the inner block without passing
    through the dispose call. Using gotos would contribute nothing except
    make it harder to assure yourself of the simplicity of the control
    flow.


    ROTFL.

    "A rose by any other name would smell as sweet." E. Dijkstra?

    'break' is just another name for 'goto label'. Fortran offers
    'cycle' and 'exit' to either return to the top of a loop (
    similar to C's 'continue') or to jump out of loop. Fortran
    has named constructs, so one can use 'cycle' and 'exit' on
    (deeply?) nested constructs.

    outer: do i = 1, 10
    ...
    inner: do j = 1, 10
    ...
    if (condition 1) cycle inner
    ...
    if (condition 2) exit outer
    ...
    if (condition 3) exit inner
    ...
    end do inner
    ...
    end do outer

    PS: We're still waiting on a definition of "storage allocation"
    and the cleanup required when jumping out of a do-loop in
    Fortran?

    PPS: rust and folklore removed again.
    --
    steve
    --
    steve

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Keith Thompson@Keith.S.Thompson+u@gmail.com to comp.lang.fortran,comp.lang.c++ on Thu Oct 22 21:21:15 2026
    From Newsgroup: comp.lang.fortran

    "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> writes:
    [...]
    'break' is just another name for 'goto label'. Fortran offers
    'cycle' and 'exit' to either return to the top of a loop (
    similar to C's 'continue') or to jump out of loop. Fortran
    has named constructs, so one can use 'cycle' and 'exit' on
    (deeply?) nested constructs.

    Any given C break statement is equivalent to a goto statement that
    jumps just after the enclosing loop or switch statement.

    But "break" is useful because it can't branch to any arbitrary point
    in the enclosing function. It can only break out of a specific
    enclosing construct. That makes the code easier to read and write.

    BTW, the next C standard is planned to add named loops and breaks,
    which are also proposed for C++. Some C compilers already implement
    them as an extension.

    [...]
    --
    Keith Thompson (The_Other_Keith) Keith.S.Thompson+u@gmail.com
    void Void(void) { Void(); } /* The recursive call of the void */
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 04:22:13 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 04:10:39 -0000 (UTC), Steven G. Kargl wrote:

    On Fri, 23 Oct 2026 03:33:44 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    So you can see there is no way out of the inner block without passing
    through the dispose call.

    'break' is just another name for 'goto label'.

    Using gotos would contribute nothing except make it harder to
    assure yourself of the simplicity of the control flow.

    PS: We're still waiting on a definition of "storage allocation"

    ... allocate object pointer ...

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 22:29:45 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach if
    you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to
    initialize it?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 22 22:31:07 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 8:21 PM, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.

    I gather thererCOs been a proposal thatrCOs been kicking around for some years, to adopt something based on Cairo
    <https://www.cairographics.org/>.

    That's a fairly decent one.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.lang.fortran,comp.lang.c++ on Fri Oct 23 05:43:56 2026
    From Newsgroup: comp.lang.fortran

    Keith Thompson <Keith.S.Thompson+u@gmail.com> schrieb:
    "Steven G. Kargl" <sgk@REMOVEtroutmask.apl.washington.edu> writes:
    [...]
    'break' is just another name for 'goto label'. Fortran offers
    'cycle' and 'exit' to either return to the top of a loop (
    similar to C's 'continue') or to jump out of loop. Fortran
    has named constructs, so one can use 'cycle' and 'exit' on
    (deeply?) nested constructs.

    Any given C break statement is equivalent to a goto statement that
    jumps just after the enclosing loop or switch statement.

    But "break" is useful because it can't branch to any arbitrary point
    in the enclosing function. It can only break out of a specific
    enclosing construct. That makes the code easier to read and write.

    The goto usually isn't the problem, you see it and you see where its
    target is.

    It is the "come from". You see a label, and you wonder what the
    state of the program is when you arrive there, and (if applicable)
    which of the several gotos went there.

    For error handling, this can be a win.

    BTW, the next C standard is planned to add named loops and breaks,
    which are also proposed for C++. Some C compilers already implement
    them as an extension.

    Makes sense. Fortran has had them for a looong time.
    --
    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 Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 05:54:44 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 04:22:13 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 04:10:39 -0000 (UTC), Steven G. Kargl wrote:

    On Fri, 23 Oct 2026 03:33:44 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    So you can see there is no way out of the inner block without passing
    through the dispose call.

    'break' is just another name for 'goto label'.

    Using gotos would contribute nothing except make it harder to
    assure yourself of the simplicity of the control flow.

    PS: We're still waiting on a definition of "storage allocation"

    ... allocate object pointer ...


    Nice use of quoting without adding context.

    It's okay to admit that you have no idea how Fortran
    works when one uses a goto to jump out of a do loop.
    There is no cleanup of "storage allocation".
    --
    steve
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 06:25:09 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    IrCOm assuming that all that BASIC programming hasnrCOt got to your head,
    and yourCOre not serious. ;)
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 06:27:10 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 22:31:07 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:21 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a
    user interface programming model for quite a long time.

    First they need a standardized graphics API.

    I gather thererCOs been a proposal thatrCOs been kicking around for
    some years, to adopt something based on Cairo
    <https://www.cairographics.org/>.

    That's a fairly decent one.

    It is (based on PostScript but goes beyond it), but the draft proposal
    IrCOve seen is somewhat butchered. No text/font API, for a start.

    The JavaScript browser-based 2D Canvas API is also based on Cairo, and
    that was also butchered, albeit in a different way.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 06:29:03 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 05:43:56 -0000 (UTC), Thomas Koenig wrote:

    Keith Thompson <Keith.S.Thompson+u@gmail.com> schrieb:

    But "break" is useful because it can't branch to any arbitrary
    point in the enclosing function. It can only break out of a
    specific enclosing construct. That makes the code easier to read
    and write.

    The goto usually isn't the problem, you see it and you see where its
    target is.

    It doesnrCOt scale.

    My example was starting simple, but I intend to work my way gradually
    up as others ask for 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 Fri Oct 23 07:58:39 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 16:02:35 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:
    boltar@battlestar.co.uk writes:
    Virtual machine? Wrong language , comp.lang.java is that way --->

    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.

    Its a fictious apple. All it means in reality is intermediate code output
    by the compiler - but then in the gnu and llvm tool chains for example ALL the compilers AFAIK do that, there's nothing unique to C/C++.

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

    There have been, in the past, threading models that support both
    hardware threads and pure software threads (e.g. SVR4.2ES/MP)
    in a single application. It was not a joke then, it's not a joke now.

    It was a joke because as soon as garbage collection happened all the green threads hung.

    --- 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 23 08:01:25 2026
    From Newsgroup: comp.lang.fortran

    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.

    --- 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 Fri Oct 23 16:02:51 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 4:41 AM, Lynn McGuire wrote:
    On 10/21/2026 8:51 PM, Johann 'Myrkraverk' Oskarsson wrote:
    On 10/22/2026 2:48 AM, boltar@battlestar.co.uk wrote:
    On Wed, 21 Oct 2026 20:26:29 +0200
    David Brown <david.brown@hesbynett.no> wrote:
    On 21/10/2026 20:02, boltar@battlestar.co.uk wrote:
    Take a look around you. How many new startups are recruiting C++ devs? >>>>>

    We see it all the time.-a Of course, different programming fields
    want different languages - C++ is suitable for some things, and less
    so for other things.-a There is no one language to fit all usage.

    There's plenty I don't like about C++ too.-a But I don't have some
    weird conspiracy theory about how it is being destroyed by some
    ivory tower academics that want C++ to be hard so that they can look
    smart, or whatever your delusions are.

    Not sure why you think its conspiracy anything. I use the language on a
    daily basis and everytime a new version comes out I hope they've added
    something useful but since 2014 its been a law of diminishing returns.
    Plus there's unexplained omissions - eg threads have been part of the
    core
    language since 2011. Great, but what about processes? When do we get
    them?
    Sure, I could just use fork() but then I could also just use
    pthread_create()
    too.

    There are what, three process models to wrap up?-a The Unix/Linux model,
    the N.T. model, and OpenVMS.

    If you need anything too different from those three, you can just fail
    with a compilation error on #include <process> or whatever.

    It isn't too hard to create a modern abstraction that does mostly the
    right thing.

    Now add the User Interface systems for the operating systems.-a And the current Apple system does not even have a C++ user interface.

    I have been advocating for quite a while that C++ should add a user interface programming model for quite a long time.

    Lynn

    In my opinion, it was a tragedy they didn't in C++98.

    In the mean time, I've been using IUP. Mostly because I use C, and not
    C++ for my own projects. And since it's C, it should be usable in both
    Rust and Fortran with a simple foreign function wrapper; but I have not
    done that yet.

    Note, IUP already existed in 1997, and could have been used as a base
    for a C++ GUI -- though I would expect the interface to be STL-ified to
    be consistent with the rest of C++.

    Best wishes, and happy user interfaces.
    --
    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 Fri Oct 23 08:03:45 2026
    From Newsgroup: comp.lang.fortran

    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?

    --- 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 23 08:05:13 2026
    From Newsgroup: comp.lang.fortran

    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.

    --- 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 Fri Oct 23 16:06:47 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 3:58 PM, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 16:02:35 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:

    boltar@battlestar.co.uk writes:

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

    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.

    Its a fictious apple. All it means in reality is intermediate code output
    by the compiler - but then in the gnu and llvm tool chains for example ALL the
    compilers AFAIK do that, there's nothing unique to C/C++.

    There is at least one -- now quite old -- C++ compiler that goes direct-
    ly to machine code, and doesn't output any assembly at all. That's Open Watcom.

    And if you want to use that compiler abstractly, you can use DOS [1] as
    a physical manifestation of the /abstract machine/.

    [1] MS-DOS, PC-DOS, DR-DOS, FreeDOS -- I'm not picky.
    --
    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 Fri Oct 23 08:10:17 2026
    From Newsgroup: comp.lang.fortran

    On Thu, 22 Oct 2026 15:41:15 -0500
    Lynn McGuire <lynnmcguire5@gmail.com> gabbled:
    On 10/21/2026 8:51 PM, Johann 'Myrkraverk' Oskarsson wrote:
    It isn't too hard to create a modern abstraction that does mostly the
    right thing.

    Now add the User Interface systems for the operating systems. And the >current Apple system does not even have a C++ user interface.

    Apple have their typical walled garden approach to OS development. They support the basic posix system and a subset of their OS specific system API
    as a C API, but if you want to do anything more in depth and not resort to a higher level language such as Python you'll have to use Objective-C (god help us) or Swift. Consequently very few people bother.

    I have been advocating for quite a while that C++ should add a user >interface programming model for quite a long time.

    Problem with that is you end up with a lowest common denominator version that Java has. Looks awful and often doesn't do what you want.


    --- 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 23 08:14:41 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 16:02:51 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> gabbled:
    On 10/23/2026 4:41 AM, Lynn McGuire wrote:
    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    Lynn

    In my opinion, it was a tragedy they didn't in C++98.

    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.

    --- 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 Fri Oct 23 16:15:23 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 4:01 PM, boltar@caprica.universe wrote:
    Programming isn't pure engineering - its a combination of engineering, logic, art and a trade.

    And sometimes mathematics. More than one programmer has had to invent
    or simplify a mathematical formula to get things to run.

    I have anecdata, and I presume everyone else here does too.
    --
    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 Fri Oct 23 08:16:32 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 16:15:23 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> gabbled:
    On 10/23/2026 4:01 PM, boltar@caprica.universe wrote:
    Programming isn't pure engineering - its a combination of engineering, logic,

    art and a trade.

    And sometimes mathematics. More than one programmer has had to invent

    True.

    --- 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 Fri Oct 23 16:22:06 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 4:14 PM, boltar@caprica.universe wrote:
    On Fri, 23 Oct 2026 16:02:51 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> gabbled:
    On 10/23/2026 4:41 AM, Lynn McGuire wrote:
    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    Lynn

    In my opinion, it was a tragedy they didn't in C++98.

    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,

    https://iup.sf.net/

    already existed, and abstracted both X11 and Win32, and -- presumably --
    Win 3.1 as well. Note that some of that circle is squared with Canvas-
    Draw and an image library, as separate projcets; both on sf.net.

    Nowadays, or last time I was paying attention to the mailing list, some-
    one else is supplying a backend for Apple computers. So all of this ex-
    ists, and has since the mid-90s.


    So my take on it, is that the C++ standards committee has been lazy for
    the past thirty years.
    --
    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 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 23 11:42:38 2026
    From Newsgroup: comp.lang.fortran

    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.

    --- 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 23 11:56:23 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 16:06:47 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 10/23/2026 3:58 PM, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 16:02:35 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:

    boltar@battlestar.co.uk writes:

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


    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.

    Its a fictious apple. All it means in reality is intermediate code
    output by the compiler - but then in the gnu and llvm tool chains
    for example ALL the compilers AFAIK do that, there's nothing unique
    to C/C++.

    There is at least one -- now quite old -- C++ compiler that goes
    direct- ly to machine code, and doesn't output any assembly at all.
    That's Open Watcom.

    And if you want to use that compiler abstractly, you can use DOS [1]
    as a physical manifestation of the /abstract machine/.

    [1] MS-DOS, PC-DOS, DR-DOS, FreeDOS -- I'm not picky.


    DOS/360 (originally simply DOS) would not do it?



    --- 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 Fri Oct 23 17:15:05 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 4:56 PM, Michael S wrote:
    On Fri, 23 Oct 2026 16:06:47 +0800
    Johann 'Myrkraverk' Oskarsson <johann@myrkraverk.invalid> wrote:

    On 10/23/2026 3:58 PM, boltar@caprica.universe wrote:
    On Thu, 22 Oct 2026 16:02:35 GMT
    scott@slp53.sl.home (Scott Lurndal) gabbled:

    boltar@battlestar.co.uk writes:

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


    The C/C++ "Virtual Machine Model" as described in the language
    specifications is an apple.

    Its a fictious apple. All it means in reality is intermediate code
    output by the compiler - but then in the gnu and llvm tool chains
    for example ALL the compilers AFAIK do that, there's nothing unique
    to C/C++.

    There is at least one -- now quite old -- C++ compiler that goes
    direct- ly to machine code, and doesn't output any assembly at all.
    That's Open Watcom.

    And if you want to use that compiler abstractly, you can use DOS [1]
    as a physical manifestation of the /abstract machine/.

    [1] MS-DOS, PC-DOS, DR-DOS, FreeDOS -- I'm not picky.


    DOS/360 (originally simply DOS) would not do it?

    Not without some effort. If I understand this correctly, and I may not,
    the Open Watcom compiler suite has the 360 code generator, but it's not
    in a functional state.

    So, in that case, it's an /exercise for the reader/.
    --
    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 Fri Oct 23 09:15:59 2026
    From Newsgroup: comp.lang.fortran

    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,

    https://iup.sf.net/

    Had a look, requires Lua. No thanks.

    --- 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 23 09:18:08 2026
    From Newsgroup: comp.lang.fortran

    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.

    --- 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 Fri Oct 23 11:28:31 2026
    From Newsgroup: comp.lang.fortran

    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.

    And could you tell me where I might find that description? The word
    "virtual" appears in the C standard only when describing one of the
    committee meetings. No two of words in "virtual machine model" appear consecutively anywhere in the C++ standard.

    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". Using the accurate term would have been better, of course.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brown@david.brown@hesbynett.no to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 11:34:00 2026
    From Newsgroup: comp.lang.fortran

    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.


    I hope that never happens. There are large numbers of graphics APIs,
    with huge ranges of what they support, how they work and their balance
    between features, efficiency, portability, size, hardware support, and
    what they are used for.

    People who think C++ should have a standardised graphics API usually
    mean they want to standardise the API they use on the one application
    type that they write.


    I gather thererCOs been a proposal thatrCOs been kicking around for some years, to adopt something based on Cairo
    <https://www.cairographics.org/>.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brown@david.brown@hesbynett.no to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 11:45:49 2026
    From Newsgroup: comp.lang.fortran

    On 23/10/2026 08:25, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    IrCOm assuming that all that BASIC programming hasnrCOt got to your head,
    and yourCOre not serious. ;)

    Chris' wording is perhaps poor, but the principle is right.

    I don't know PL/I or Fortran, but in C if you have :

    typedef struct data_struct { int a; int xs[20]; } S ;

    S build_some_data(void) {
    S s;

    s.a = 123;
    for (int i = 0; i < 20; i++) s.xs[i] = i;

    return s;
    }

    void foo() {
    S s = build_some_data();
    }


    then it is typically handled as though you had written :

    void build_some_data(S * p) {
    p->a = 123;
    for (int i = 0; i < 20; i++) p->xs[i] = i;

    return;
    }

    void foo() {
    S s;
    build_some_data(&s);
    }


    That is - the caller creates the /space/ for the returned object, but
    does not do any kind of initialisation. It passes a pointer to that
    space as a hidden parameter to the function that wants to return the object.

    That principle should work fine in any language, as long as the size of
    the returned object is known by the caller code.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 10:11:46 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 11:34:00 +0200
    David Brown <david.brown@hesbynett.no> gabbled:
    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.


    I hope that never happens. There are large numbers of graphics APIs,
    with huge ranges of what they support, how they work and their balance >between features, efficiency, portability, size, hardware support, and
    what they are used for.

    People who think C++ should have a standardised graphics API usually
    mean they want to standardise the API they use on the one application

    For once we're in agreement.

    --- 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 Fri Oct 23 18:15:32 2026
    From Newsgroup: comp.lang.fortran

    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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 09:02:50 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/26 22:29, Chris M. Thomasson wrote:
    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach if
    you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to initialize it?

    That obviously wouldn't work, since then the caller would have to know something about the object beforehand. I think you'd have to depend on
    the compiler to destroy the object when it goes out of scope, unless the caller destroys it itself.
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 09:55:48 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/26 02:34, David Brown wrote:
    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.


    I hope that never happens.-a There are large numbers of graphics APIs,
    with huge ranges of what they support, how they work and their balance between features, efficiency, portability, size, hardware support, and
    what they are used for.

    People who think C++ should have a standardised graphics API usually
    mean they want to standardise the API they use on the one application
    type that they write.


    I gather thererCOs been a proposal thatrCOs been kicking around for some
    years, to adopt something based on Cairo
    <https://www.cairographics.org/>.


    You need something with subsets. At least a "basic" subset, a "full"
    subset, and something in between that satisfies most uses. Or maybe
    subsets for different purposes, but they should all be compatible.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 09:57:01 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/26 02:45, David Brown wrote:
    On 23/10/2026 08:25, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    IrCOm assuming that all that BASIC programming hasnrCOt got to your head,
    and yourCOre not serious. ;)

    Chris' wording is perhaps poor, but the principle is right.

    I don't know PL/I or Fortran, but in C if you have :

    -a-a-a-atypedef struct data_struct { int a; int xs[20]; } S ;

    -a-a-a-aS build_some_data(void) {
    -a-a-a-a-a-a-a S s;

    -a-a-a-a-a-a-a s.a = 123;
    -a-a-a-a-a-a-a for (int i = 0; i < 20; i++) s.xs[i] = i;

    -a-a-a-a-a-a-a return s;
    -a-a-a-a}

    -a-a-a-avoid foo() {
    -a-a-a-a-a-a-a S s = build_some_data();
    -a-a-a-a}


    then it is typically handled as though you had written :

    -a-a-a-avoid build_some_data(S * p) {
    -a-a-a-a-a-a-a p->a = 123;
    -a-a-a-a-a-a-a for (int i = 0; i < 20; i++) p->xs[i] = i;

    -a-a-a-a-a-a-a return;
    -a-a-a-a}

    -a-a-a-avoid foo() {
    -a-a-a-a-a-a-a S s;
    -a-a-a-a-a-a-a build_some_data(&s);
    -a-a-a-a}


    That is - the caller creates the /space/ for the returned object, but
    does not do any kind of initialisation.-a It passes a pointer to that
    space as a hidden parameter to the function that wants to return the
    object.

    That principle should work fine in any language, as long as the size of
    the returned object is known by the caller code.

    That last sentence is why it would not work fine,
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 19:19:28 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 09:02:50 -0700, Peter Flass wrote:

    On 10/22/26 22:29, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    That obviously wouldn't work, since then the caller would have to
    know something about the object beforehand.

    And what if the object didnrCOt consist of just *one*
    dynamically-allocated block, but needed links to other blocks as well?
    What if it needed objects dynamically allocated by other APIs, the
    details of which are internal to those APIs? Is the caller required to
    know about all these implementation details?

    In short, the concept doesnrCOt scale, because it completely breaks the
    concept of data abstraction.

    And it just pushes the dynamic-allocation problem elsewhere, without
    making it easier.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 19:20:50 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 05:54:44 -0000 (UTC), Steven G. Kargl wrote:

    On Fri, 23 Oct 2026 04:22:13 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 04:10:39 -0000 (UTC), Steven G. Kargl wrote:

    On Fri, 23 Oct 2026 03:33:44 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    So you can see there is no way out of the inner block without passing
    through the dispose call.

    'break' is just another name for 'goto label'.

    Using gotos would contribute nothing except make it harder to
    assure yourself of the simplicity of the control flow.

    PS: We're still waiting on a definition of "storage allocation"

    ... allocate object pointer ...


    Nice use of quoting without adding context.

    Just pointing out (in case you didnrCOt notice) that the points you were raising were already addressed in the posting you were (supposedly)
    replying to ...
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 19:25:21 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 09:55:48 -0700, Peter Flass wrote:

    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a
    user interface programming model for quite a long time.

    First they need a standardized graphics API.

    I gather thererCOs been a proposal thatrCOs been kicking around for
    some years, to adopt something based on Cairo
    <https://www.cairographics.org/>.

    You need something with subsets. At least a "basic" subset, a "full"
    subset, and something in between that satisfies most uses. Or maybe
    subsets for different purposes, but they should all be compatible.

    Cairo is not exactly a large API, you know. And it already has a full open-source implementation that can be copied.

    For reference, I had the basics of my pure-Python wrapper <https://gitlab.com/ldo/qahirah> working in about the first 3 weeks.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 19:30:58 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 16:37:37 GMT, Charlie Gibbs wrote:

    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.

    Remember that current rCLWindowsrCY actually means rCLWindows NTrCY. Which was primarily the brainchild of Dave Cutler, who came from the nest of
    Unix-haters at DEC.

    Perhaps it was the corporate culture with Bill Gates at the helm that
    attracted Cutler to Microsoft. But look at some of the boneheaded
    decisions he made (or propagated from old DOS-based Windows), just so
    NT wouldnrCOt look like Unix, which continue to haunt Microsoft to this
    day.

    In short, Gates couldnrCOt have done what Microsoft achieved on his own.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Steven G. Kargl@sgk@REMOVEtroutmask.apl.washington.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 19:38:09 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 19:20:50 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 05:54:44 -0000 (UTC), Steven G. Kargl wrote:
    On Fri, 23 Oct 2026 04:22:13 -0000 (UTC), Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 04:10:39 -0000 (UTC), Steven G. Kargl wrote:
    On Fri, 23 Oct 2026 03:33:44 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>> So you can see there is no way out of the inner block without passing >>>>> through the dispose call.

    'break' is just another name for 'goto label'.

    Using gotos would contribute nothing except make it harder to
    assure yourself of the simplicity of the control flow.

    PS: We're still waiting on a definition of "storage allocation"

    ... allocate object pointer ...


    Nice use of quoting without adding context.

    Just pointing out (in case you didnrCOt notice) that the points you were raising were already addressed in the posting you were (supposedly)
    replying to ...

    And, we are still waiting for your definition of "storage allocation"
    and its needed cleanup in the context of Fortran 77. It as been pointed
    out to you multiple times that Fortran 77 does not have dynamic memory allocation. Fortran 77 does not have pointers and it does not have
    objects. So, what is this mythical cleanup of storage allocation in
    Fortran 77?

    It's okay to admit that you were making a some generalization that
    does not apply to Fortran 77.
    --
    steve
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 12:48:58 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 11:27 PM, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:31:07 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:21 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a
    user interface programming model for quite a long time.

    First they need a standardized graphics API.

    I gather thererCOs been a proposal thatrCOs been kicking around for
    some years, to adopt something based on Cairo
    <https://www.cairographics.org/>.

    That's a fairly decent one.

    It is (based on PostScript but goes beyond it), but the draft proposal
    IrCOve seen is somewhat butchered. No text/font API, for a start.

    The JavaScript browser-based 2D Canvas API is also based on Cairo, and
    that was also butchered, albeit in a different way.

    Fwiw, Cairo is up on vcpkg, so its really easy to build and integrate
    with any MSVC project.

    https://vcpkg.io/en/package/cairo
    --- 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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 12:55:02 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 2:34 AM, David Brown wrote:
    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.


    I hope that never happens.-a There are large numbers of graphics APIs,
    with huge ranges of what they support, how they work and their balance between features, efficiency, portability, size, hardware support, and
    what they are used for.

    People who think C++ should have a standardised graphics API usually
    mean they want to standardise the API they use on the one application
    type that they write.


    I gather thererCOs been a proposal thatrCOs been kicking around for some
    years, to adopt something based on Cairo
    <https://www.cairographics.org/>.


    Fwiw, vcpkg has a lot of them, ready to automatically build and
    integrate. vcpkg is actually... Well, its pretty nice and so far...
    Seems to work for me.

    Want to use Cairo, just do it.

    https://vcpkg.io/en/package/cairo

    Actually vcpkg just builds the sucker. No manually installing mingw
    and/or cygwin or whatever fiddling on windows. Ugggg...

    Iirc, I think Bart got pissed off about manually building and/or
    installing certain things on Windows. Don't get me wrong, it was a
    bitch! But, vcpkg can help for sure.

    So far, works pretty damn nice.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 19:56:48 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 12:48:58 -0700, Chris M. Thomasson wrote:

    Fwiw, Cairo is up on vcpkg, so its really easy to build and
    integrate with any MSVC project.

    https://vcpkg.io/en/package/cairo

    Do you get Fontconfig and FreeType as well?

    I thought Windows had native equivalents to all this functionality
    anyway, yet here you are, reimplementing the entire Free Software
    stack in parallel to it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 12:57:23 2026
    From Newsgroup: comp.lang.fortran

    On 10/22/2026 11:27 PM, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:31:07 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:21 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a
    user interface programming model for quite a long time.

    First they need a standardized graphics API.

    I gather thererCOs been a proposal thatrCOs been kicking around for
    some years, to adopt something based on Cairo
    <https://www.cairographics.org/>.

    That's a fairly decent one.

    It is (based on PostScript but goes beyond it), but the draft proposal
    IrCOve seen is somewhat butchered. No text/font API, for a start.

    The JavaScript browser-based 2D Canvas API is also based on Cairo, and
    that was also butchered, albeit in a different way.

    For a gui, a pretty good one for opengl, directx, etc, is imgui. vcpkg
    has it as well:

    https://vcpkg.io/en/package/imgui
    --- 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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 19:59:11 2026
    From Newsgroup: comp.lang.fortran

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

    Did he do that on his own? Or did Paul Allen do some or possibly even
    most or all of the work?

    And how do you explain that Microsoft Windows (both the old DOS-based
    Windows and current NT-based Windows) manages to carry over so many
    bits of cruft from the 8-bit era, when it never ran on 8-bit machines?
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 13:30:42 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 12:56 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 12:48:58 -0700, Chris M. Thomasson wrote:

    Fwiw, Cairo is up on vcpkg, so its really easy to build and
    integrate with any MSVC project.

    https://vcpkg.io/en/package/cairo

    Do you get Fontconfig and FreeType as well?

    I thought Windows had native equivalents to all this functionality
    anyway, yet here you are, reimplementing the entire Free Software
    stack in parallel to it.

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

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

    On Fri, 23 Oct 2026 16:37:37 GMT, Charlie Gibbs wrote:

    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.

    Remember that current rCLWindowsrCY actually means rCLWindows NTrCY. Which was
    primarily the brainchild of Dave Cutler, who came from the nest of Unix-haters at DEC.

    Still, much of the cruft I had to deal with was present in 3.1.

    In short, Gates couldnrCOt have done what Microsoft achieved on his own.

    Sort of like an evil genius commanding his legion of minions...
    --
    /~\ 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: comp.lang.fortran

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 13:43:27 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 9:57 AM, Peter Flass wrote:
    On 10/23/26 02:45, David Brown wrote:
    On 23/10/2026 08:25, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the >>>>> caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    IrCOm assuming that all that BASIC programming hasnrCOt got to your head, >>> and yourCOre not serious. ;)

    Chris' wording is perhaps poor, but the principle is right.

    I don't know PL/I or Fortran, but in C if you have :

    -a-a-a-a-atypedef struct data_struct { int a; int xs[20]; } S ;

    -a-a-a-a-aS build_some_data(void) {
    -a-a-a-a-a-a-a-a S s;

    -a-a-a-a-a-a-a-a s.a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) s.xs[i] = i;

    -a-a-a-a-a-a-a-a return s;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s = build_some_data();
    -a-a-a-a-a}


    then it is typically handled as though you had written :

    -a-a-a-a-avoid build_some_data(S * p) {
    -a-a-a-a-a-a-a-a p->a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) p->xs[i] = i;

    -a-a-a-a-a-a-a-a return;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s;
    -a-a-a-a-a-a-a-a build_some_data(&s);
    -a-a-a-a-a}


    That is - the caller creates the /space/ for the returned object, but
    does not do any kind of initialisation.-a It passes a pointer to that
    space as a hidden parameter to the function that wants to return the
    object.

    That principle should work fine in any language, as long as the size
    of the returned object is known by the caller code.

    That last sentence is why it would not work fine,

    if a dynamic object is returned, we need to handle its lifetime. __________________________
    // pseudo code

    struct foo
    {
    struct bar* m_bar = nullptr;
    int m_a = 0;
    double m_b = .42;
    };


    foo_init(
    struct foo* const self
    ) {
    // assume foobar_lib_create succeeded...
    self->m_bar = foobar_lib_create(...);
    // now we must destroy it in foo_destroy after
    // the caller logic is done with it.
    }


    foo_destroy(
    struct foo const* const self
    ) {
    foobar_lib_destroy(self->m_bar);
    }
    __________________________

    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 13:50:34 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 9:57 AM, Peter Flass wrote:
    On 10/23/26 02:45, David Brown wrote:
    On 23/10/2026 08:25, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the >>>>> caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    IrCOm assuming that all that BASIC programming hasnrCOt got to your head, >>> and yourCOre not serious. ;)

    Chris' wording is perhaps poor, but the principle is right.

    I don't know PL/I or Fortran, but in C if you have :

    -a-a-a-a-atypedef struct data_struct { int a; int xs[20]; } S ;

    -a-a-a-a-aS build_some_data(void) {
    -a-a-a-a-a-a-a-a S s;

    -a-a-a-a-a-a-a-a s.a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) s.xs[i] = i;

    -a-a-a-a-a-a-a-a return s;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s = build_some_data();
    -a-a-a-a-a}


    then it is typically handled as though you had written :

    -a-a-a-a-avoid build_some_data(S * p) {
    -a-a-a-a-a-a-a-a p->a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) p->xs[i] = i;

    -a-a-a-a-a-a-a-a return;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s;
    -a-a-a-a-a-a-a-a build_some_data(&s);
    -a-a-a-a-a}


    That is - the caller creates the /space/ for the returned object, but
    does not do any kind of initialisation.-a It passes a pointer to that
    space as a hidden parameter to the function that wants to return the
    object.

    That principle should work fine in any language, as long as the size
    of the returned object is known by the caller code.

    That last sentence is why it would not work fine,

    Or have an API that can give us the size of the object the caller needs
    to create. So, again pseudo code:

    size = foolib_create_get_size(...);
    foo_alloc_req fareq = { };
    foolib_create_get_alloc_req(&fareq);

    foo = create_on_the_stack_etc(size, &fareq);

    // The API would have all of that as prerequisites so the caller knows
    // about it. Alignment requirements, etc.

    foolib_init(foo);

    ...

    foolib_destroy(foo);
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 13:56:49 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 09:02:50 -0700, Peter Flass wrote:

    On 10/22/26 22:29, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    That obviously wouldn't work, since then the caller would have to
    know something about the object beforehand.

    And what if the object didnrCOt consist of just *one*
    dynamically-allocated block, but needed links to other blocks as well?
    What if it needed objects dynamically allocated by other APIs, the
    details of which are internal to those APIs? Is the caller required to
    know about all these implementation details?

    In short, the concept doesnrCOt scale, because it completely breaks the concept of data abstraction.

    And it just pushes the dynamic-allocation problem elsewhere, without
    making it easier.

    It can be made to work, and if it fits in with your "scheme", okay, if
    not so what? Have an API that can give us the size of the object the
    caller needs to create. So, again pseudo code:

    size = foolib_create_get_size(...);
    foo_alloc_req fareq = { };
    foolib_create_get_alloc_req(&fareq);

    foo = create_on_the_stack_etc(size, &fareq);

    // The API would have all of that as prerequisites so the caller knows
    // about it. Alignment requirements, etc.

    foolib_init(foo);

    ...

    foolib_destroy(foo);


    The caller can gain the size, and the alignment requirements up front.
    It can allocate it using any of its means. Then use that to call into
    the lib. It works.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 14:00:25 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 9:02 AM, Peter Flass wrote:
    On 10/22/26 22:29, Chris M. Thomasson wrote:
    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach if
    you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    That obviously wouldn't work, since then the caller would have to know something about the object beforehand. I think you'd have to depend on
    the compiler to destroy the object when it goes out of scope, unless the caller destroys it itself.

    Knowing a size and an alignment requirement doesn't mean the caller
    knows how the object works or what fields it holds. It just means they
    know the dimensions of the box. They get a handle or a raw pointer,
    while the internal layout remains entirely hidden behind the API. That
    is textbook encapsulation
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Thomas Koenig@tkoenig@netcologne.de to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 21:00:30 2026
    From Newsgroup: comp.lang.fortran

    David Brown <david.brown@hesbynett.no> schrieb:
    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.


    I hope that never happens.

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

    Works for all programming languages as long as they do text I/O.

    There are large numbers of graphics APIs,
    with huge ranges of what they support, how they work and their balance between features, efficiency, portability, size, hardware support, and
    what they are used for.

    I guess mine is an example rather restricted graphics API, then :-)
    --
    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 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: comp.lang.fortran

    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 Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 05:14:55 2026
    From Newsgroup: comp.lang.fortran

    On 10/24/2026 5:00 AM, Thomas Koenig wrote:
    David Brown <david.brown@hesbynett.no> schrieb:
    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.


    I hope that never happens.

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

    Works for all programming languages as long as they do text I/O.

    There are large numbers of graphics APIs,
    with huge ranges of what they support, how they work and their balance
    between features, efficiency, portability, size, hardware support, and
    what they are used for.

    I guess mine is an example rather restricted graphics API, then :-)


    If I remember the manual correctly, Open Watcom Fortran 77 has Win 3.1 abstractions. Those never got ported to Win 95+, as far as I know of,
    so didn't last. I should try it one of these days, and see if it still
    works.
    --
    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 Johann 'Myrkraverk' Oskarsson@johann@myrkraverk.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 05:19:54 2026
    From Newsgroup: comp.lang.fortran

    On 10/24/2026 3:38 AM, Steven G. Kargl wrote:
    On Fri, 23 Oct 2026 19:20:50 -0000 (UTC), Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 05:54:44 -0000 (UTC), Steven G. Kargl wrote:
    On Fri, 23 Oct 2026 04:22:13 -0000 (UTC), Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 04:10:39 -0000 (UTC), Steven G. Kargl wrote:
    On Fri, 23 Oct 2026 03:33:44 -0000 (UTC), Lawrence DrCOOliveiro wrote: >>>>>> So you can see there is no way out of the inner block without passing >>>>>> through the dispose call.

    'break' is just another name for 'goto label'.

    Using gotos would contribute nothing except make it harder to
    assure yourself of the simplicity of the control flow.

    PS: We're still waiting on a definition of "storage allocation"

    ... allocate object pointer ...


    Nice use of quoting without adding context.

    Just pointing out (in case you didnrCOt notice) that the points you were
    raising were already addressed in the posting you were (supposedly)
    replying to ...

    And, we are still waiting for your definition of "storage allocation"
    and its needed cleanup in the context of Fortran 77. It as been pointed
    out to you multiple times that Fortran 77 does not have dynamic memory allocation. Fortran 77 does not have pointers and it does not have
    objects. So, what is this mythical cleanup of storage allocation in
    Fortran 77?

    It's okay to admit that you were making a some generalization that
    does not apply to Fortran 77.


    Dear Steven,

    I'm sure you're well aware of the nerd-posturing that prohibits people
    from accepting their mistakes, or admit lacking in any programming ca-
    pacity. I believe Lawrence will never cop to any fault, because it'll
    /lower his social standing/ among the trolls of comp.lang.c++.


    So best wishes, and happy waiting forever for the nerds to apologize!
    --
    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 14:29:22 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:
    That obviously wouldn't work, since then the caller would have to
    know something about the object beforehand.

    non sequitur?
    --- 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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 22:42:21 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:

    In short, the concept doesnrCOt scale, because it completely breaks
    the concept of data abstraction.

    And it just pushes the dynamic-allocation problem elsewhere,
    without making it easier.

    It can be made to work ...

    IrCOm sure itrCOs *possible*, but what is the *point*?

    The whole aim of levels of abstraction is to tame the multi-headed
    beast of complexity that is computer programming. What you are doing
    here is breaking down those levels, all in the aid of, I donrCOt know,
    just to keep using gotos in your code, or something.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 22:43:11 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 14:29:22 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:

    That obviously wouldn't work, since then the caller would have to
    know something about the object beforehand.

    non sequitur?

    I donrCOt care, because ... I didnrCOt say that.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 22:46:17 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 12:55:02 -0700, Chris M. Thomasson wrote:

    Fwiw, vcpkg has a lot of them, ready to automatically build and
    integrate. vcpkg is actually... Well, its pretty nice and so far...
    Seems to work for me.

    How does it work for end-users? Are your dependencies automatically
    brought in when they install your package? How are they kept
    up-to-date?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 22:49:31 2026
    From Newsgroup: comp.lang.fortran

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

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

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

    Look at successors like Cairo, and you clearly see the PostScript
    influence. And yet they are definitely more modern in their approach.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 22:50:33 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 20:28:07 GMT, Charlie Gibbs wrote:

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

    In short, Gates couldnrCOt have done what Microsoft achieved on his own.

    Sort of like an evil genius commanding his legion of minions...

    He set the standard for the corporate culture at Microsoft!

    A culture which persists to this day ...
    --- 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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 22:57:28 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 13:02:44 -0700, Chris M. Thomasson wrote:

    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!

    My first exposure to a real computer system was a DEC PDP-11. I
    remember the first time I saw an Apple II running LOGO. Somebody tried
    telling it to do a file I/O command without a floppy in the drive. It
    ground away for a few seconds, and then produced an error message --
    of course.

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

    IrCOm having trouble with the disk.

    To me, that was like a splash in the face with a pail of cold water.
    The idea of an error message phrased in plain, approachable language
    (using a first-person pronoun, even) instead of technical terms?? That
    was a revelation.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 23:31:41 2026
    From Newsgroup: comp.lang.fortran

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

    On Fri, 23 Oct 2026 13:02:44 -0700, Chris M. Thomasson wrote:

    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!

    My first exposure to a real computer system was a DEC PDP-11. I
    remember the first time I saw an Apple II running LOGO. Somebody tried telling it to do a file I/O command without a floppy in the drive. It
    ground away for a few seconds, and then produced an error message --
    of course.

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

    IrCOm having trouble with the disk.

    To me, that was like a splash in the face with a pail of cold water.
    The idea of an error message phrased in plain, approachable language
    (using a first-person pronoun, even) instead of technical terms?? That
    was a revelation.

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

    Think of it from a support person's point of view. A user calls
    and says, "I have an error message." "OK," you reply, "what is
    the message?" "It doesn't work." That's what the user would have
    said anyway - we've just wasted some time, and we still have to
    start the same old game of Twenty Questions.

    I'm not saying that we should go back to the days of cryptic error
    codes. But an error message can be both friendly and helpful.
    For your case, how about something like "There is no disk in the
    drive" or "The disk is write-protected"? And then follow it with
    an error code for those of us who know how to interpret them.
    Users shouldn't be made to guess what the computer already knows.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to 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: comp.lang.fortran

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 16:58:04 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 3:46 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 12:55:02 -0700, Chris M. Thomasson wrote:

    Fwiw, vcpkg has a lot of them, ready to automatically build and
    integrate. vcpkg is actually... Well, its pretty nice and so far...
    Seems to work for me.

    How does it work for end-users? Are your dependencies automatically
    brought in when they install your package? How are they kept
    up-to-date?

    Oh yeah. In your build directory, say Debug or Release, it has all of
    the built shared libs and everything you need to run it.

    Keeping them up to date is, afaict, manual.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 17:00:00 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 4:58 PM, Chris M. Thomasson wrote:
    On 10/23/2026 3:46 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 12:55:02 -0700, Chris M. Thomasson wrote:

    Fwiw, vcpkg has a lot of them, ready to automatically build and
    integrate. vcpkg is actually... Well, its pretty nice and so far...
    Seems to work for me.

    How does it work for end-users? Are your dependencies automatically
    brought in when they install your package? How are they kept
    up-to-date?

    Oh yeah. In your build directory, say Debug or Release, it has all of
    the built shared libs and everything you need to run it.

    Keeping them up to date is, afaict, manual.

    In the sense of going back to vcpkg, seeing if there is a new version, building it, and it updates everything. Then go back to your project(s),
    and rebuild them, or they might just link up.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 17:01:28 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 3:42 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:

    In short, the concept doesnrCOt scale, because it completely breaks
    the concept of data abstraction.

    And it just pushes the dynamic-allocation problem elsewhere,
    without making it easier.

    It can be made to work ...

    IrCOm sure itrCOs *possible*, but what is the *point*?

    The whole aim of levels of abstraction is to tame the multi-headed
    beast of complexity that is computer programming. What you are doing
    here is breaking down those levels, all in the aid of, I donrCOt know,
    just to keep using gotos in your code, or something.

    Well, not about goto's and such. Just so a lib can inform the caller as
    to what it needs to work with. The caller sets it up, then calls into
    the init etc. Its being used in a lot of places. Take Vulkan.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 17:01:50 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 3:43 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 14:29:22 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:

    That obviously wouldn't work, since then the caller would have to
    know something about the object beforehand.

    non sequitur?

    I donrCOt care, because ... I didnrCOt say that.

    Oh sorry.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Oct 23 17:04:45 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/26 16:31, Charlie Gibbs wrote:
    On 2026-10-23, Lawrence DrCOOliveiro <ldo@nz.invalid> wrote:

    On Fri, 23 Oct 2026 13:02:44 -0700, Chris M. Thomasson wrote:

    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!

    My first exposure to a real computer system was a DEC PDP-11. I
    remember the first time I saw an Apple II running LOGO. Somebody tried
    telling it to do a file I/O command without a floppy in the drive. It
    ground away for a few seconds, and then produced an error message --
    of course.

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

    IrCOm having trouble with the disk.

    To me, that was like a splash in the face with a pail of cold water.
    The idea of an error message phrased in plain, approachable language
    (using a first-person pronoun, even) instead of technical terms?? That
    was a revelation.

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

    Think of it from a support person's point of view. A user calls
    and says, "I have an error message." "OK," you reply, "what is
    the message?" "It doesn't work." That's what the user would have
    said anyway - we've just wasted some time, and we still have to
    start the same old game of Twenty Questions.

    I'm not saying that we should go back to the days of cryptic error
    codes. But an error message can be both friendly and helpful.
    For your case, how about something like "There is no disk in the
    drive" or "The disk is write-protected"? And then follow it with
    an error code for those of us who know how to interpret them.
    Users shouldn't be made to guess what the computer already knows.


    I like messages with codes AND descriptive text.
    --- 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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 03:33:34 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 17:01:28 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 3:42 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:

    In short, the concept doesnrCOt scale, because it completely breaks
    the concept of data abstraction.

    And it just pushes the dynamic-allocation problem elsewhere,
    without making it easier.

    It can be made to work ...

    IrCOm sure itrCOs *possible*, but what is the *point*?

    The whole aim of levels of abstraction is to tame the multi-headed
    beast of complexity that is computer programming. What you are
    doing here is breaking down those levels, all in the aid of, I
    donrCOt know, just to keep using gotos in your code, or something.

    Well, not about goto's and such. Just so a lib can inform the caller
    as to what it needs to work with. The caller sets it up, then calls
    into the init etc. Its being used in a lot of places. Take Vulkan.

    Where in Vulkan? Exposing implementation details to the caller not
    only increases complexity, it also limits the implementorrCOs ability to
    change those details later.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 03:39:07 2026
    From Newsgroup: comp.lang.fortran

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

    On 10/23/2026 3:46 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 12:55:02 -0700, Chris M. Thomasson wrote:

    Fwiw, vcpkg has a lot of them, ready to automatically build and
    integrate. vcpkg is actually... Well, its pretty nice and so
    far... Seems to work for me.

    How does it work for end-users? Are your dependencies automatically
    brought in when they install your package? How are they kept
    up-to-date?

    Oh yeah. In your build directory, say Debug or Release, it has all
    of the built shared libs and everything you need to run it.

    Keeping them up to date is, afaict, manual.

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

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

    Example from my system:

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

    Where did these come from?

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

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

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

    The runtime library is always versioned. This allows multiple versions
    of the library to be present at once, with some older packages, that havenrCOt been rebuilt, still depending on an older version, while up-to-date packages make use of the newer version.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 03:44:58 2026
    From Newsgroup: comp.lang.fortran

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

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

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

    IrCOm having trouble with the disk.

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

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

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

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

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

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

    rCiAnybody who had made much use of floppy disks on micros, anyway.
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 08:18:32 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 23 Oct 2026 19:30:58 -0000 (UTC)
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> gabbled:
    On Fri, 23 Oct 2026 16:37:37 GMT, Charlie Gibbs wrote:

    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.

    Remember that current rCLWindowsrCY actually means rCLWindows NTrCY. Which was >primarily the brainchild of Dave Cutler, who came from the nest of >Unix-haters at DEC.

    Perhaps it was the corporate culture with Bill Gates at the helm that >attracted Cutler to Microsoft. But look at some of the boneheaded
    decisions he made (or propagated from old DOS-based Windows), just so
    NT wouldnrCOt look like Unix, which continue to haunt Microsoft to this
    day.

    People forget that Microsoft had its own version of unix - xenix (which it eventually sold to SCO). They could easily have put a Windows-like GUI on top with or without X Windows underneath, and a DOS compat API to run DOS programs. But they didn't - they wasted time and money creating NT which was a piss
    poor imitation and even today, no sane IT manager would use Windows Server in
    a mission critical 24/7/265 rack setup.

    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 David Brown@david.brown@hesbynett.no to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 12:38:36 2026
    From Newsgroup: comp.lang.fortran

    On 23/10/2026 18:55, Peter Flass wrote:
    On 10/23/26 02:34, David Brown wrote:
    On 23/10/2026 05:21, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 15:41:15 -0500, Lynn McGuire wrote:

    I have been advocating for quite a while that C++ should add a user
    interface programming model for quite a long time.

    First they need a standardized graphics API.


    I hope that never happens.-a There are large numbers of graphics APIs,
    with huge ranges of what they support, how they work and their balance
    between features, efficiency, portability, size, hardware support, and
    what they are used for.

    People who think C++ should have a standardised graphics API usually
    mean they want to standardise the API they use on the one application
    type that they write.


    I gather thererCOs been a proposal thatrCOs been kicking around for some >>> years, to adopt something based on Cairo
    <https://www.cairographics.org/>.


    You need something with subsets. At least a "basic" subset, a "full"
    subset, and something in between that satisfies most uses. Or maybe
    subsets for different purposes, but they should all be compatible.

    You can't do that for GUI's. All you get is a collection of subsets
    that are wrong for many people, and not nearly enough for most of them.

    Look at Python. It has a standard gui interface in the standard library
    - TKInter. Of serious Python programs with guis, it probably has a
    market share of a few percent - it's pretty much pointless having it in
    the standard library.

    There are a large number of gui toolkits used - QT, wx, GTK, SDL,
    "immediate mode" guis, embedded web browsers, etc. I have no
    statistics, but I doubt if there are any that have more than about 10% "market" share. Any many of these have wildly different paradigms - you
    can't easily combine them for a subset or abstraction.

    A standardised gui for C++ always sounds like a nice idea, but I can't
    see it being at all practical as part of the C++ standards process. At
    best, it could be a parallel setup with its own scheduling and its own publications. Trying to fit a gui into the model use for creating and maintaining the C++ standards would 5 years to produce a document that
    is 4 times the size of the current standard, 8 years out of date, and
    would be ignored by 95% of people writing gui programs in C++. And
    that's assuming you ignore one of the major users of C++ - the embedded
    world.



    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From David Brown@david.brown@hesbynett.no to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 12:43:02 2026
    From Newsgroup: comp.lang.fortran

    On 23/10/2026 18:57, Peter Flass wrote:
    On 10/23/26 02:45, David Brown wrote:
    On 23/10/2026 08:25, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach
    if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the >>>>> caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    IrCOm assuming that all that BASIC programming hasnrCOt got to your head, >>> and yourCOre not serious. ;)

    Chris' wording is perhaps poor, but the principle is right.

    I don't know PL/I or Fortran, but in C if you have :

    -a-a-a-a-atypedef struct data_struct { int a; int xs[20]; } S ;

    -a-a-a-a-aS build_some_data(void) {
    -a-a-a-a-a-a-a-a S s;

    -a-a-a-a-a-a-a-a s.a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) s.xs[i] = i;

    -a-a-a-a-a-a-a-a return s;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s = build_some_data();
    -a-a-a-a-a}


    then it is typically handled as though you had written :

    -a-a-a-a-avoid build_some_data(S * p) {
    -a-a-a-a-a-a-a-a p->a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) p->xs[i] = i;

    -a-a-a-a-a-a-a-a return;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s;
    -a-a-a-a-a-a-a-a build_some_data(&s);
    -a-a-a-a-a}


    That is - the caller creates the /space/ for the returned object, but
    does not do any kind of initialisation.-a It passes a pointer to that
    space as a hidden parameter to the function that wants to return the
    object.

    That principle should work fine in any language, as long as the size
    of the returned object is known by the caller code.

    That last sentence is why it would not work fine,

    OK. Knowing the size of the returned object is an absolute requirement
    for pre-allocation by the caller, and it is a requirement that is fine
    for a lot of situations and a lot of languages. But if it is not the
    case for PL/I, Fortran, or any other particular language (or particular function in any language), then I fully agree - the object's space can't
    be handled by the caller.

    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 13:04:38 2026
    From Newsgroup: comp.lang.fortran

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

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

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

    IrCOm having trouble with the disk.

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

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

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

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

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

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

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

    Iirc, BASIC had a fun error. I cannot remember the damn exact phrase, it
    was something like expression too complex or something.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 13:26:07 2026
    From Newsgroup: comp.lang.fortran

    On 10/23/2026 8:33 PM, Lawrence DrCOOliveiro wrote:
    On Fri, 23 Oct 2026 17:01:28 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 3:42 PM, Lawrence DrCOOliveiro wrote:

    On Fri, 23 Oct 2026 13:56:49 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 12:19 PM, Lawrence DrCOOliveiro wrote:

    In short, the concept doesnrCOt scale, because it completely breaks
    the concept of data abstraction.

    And it just pushes the dynamic-allocation problem elsewhere,
    without making it easier.

    It can be made to work ...

    IrCOm sure itrCOs *possible*, but what is the *point*?

    The whole aim of levels of abstraction is to tame the multi-headed
    beast of complexity that is computer programming. What you are
    doing here is breaking down those levels, all in the aid of, I
    donrCOt know, just to keep using gotos in your code, or something.

    Well, not about goto's and such. Just so a lib can inform the caller
    as to what it needs to work with. The caller sets it up, then calls
    into the init etc. Its being used in a lot of places. Take Vulkan.

    Where in Vulkan? Exposing implementation details to the caller not
    only increases complexity, it also limits the implementorrCOs ability to change those details later.

    Iiic, vkGetBufferMemoryRequirements and vkGetImageMemoryRequirements,
    which return a VkMemoryRequirements struct containing size, alignment,
    and memoryTypeBits. The caller allocates the memory with
    vkAllocateMemory and binds it with vkBindBufferMemory.

    Also, iirc io_uring: IORING_SETUP_NO_MMAP (Linux 6.5+) lets the caller
    supply the memory for the rings and SQE array. It must be suitably
    aligned (page or huge page), and the caller has to compute how big it
    needs to be from the entry count and flags.

    So it can be made to work.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 13:27:30 2026
    From Newsgroup: comp.lang.fortran

    On 10/24/2026 1:26 PM, Chris M. Thomasson wrote:
    Iiic, vkGetBufferMemoryRequirements and vkGetImageMemoryRequirements,
    which return a VkMemoryRequirements struct containing size, alignment,
    and memoryTypeBits. The caller allocates the memory with
    vkAllocateMemory and binds it with vkBindBufferMemory.

    Also, iirc io_uring: IORING_SETUP_NO_MMAP (Linux 6.5+) lets the caller supply the memory for the rings and SQE array. It must be suitably
    aligned (page or huge page), and the caller has to compute how big it
    needs to be from the entry count and flags.

    So it can be made to work.

    Or what about miniaudiorCOs ma_engine_get_heap_size plus ma_engine_init_preallocated
    --- 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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 21:38:42 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

    IrCOm having trouble with the disk.

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

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

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

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

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

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

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

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

    "Who is General Failure and why is he reading my disk?"
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 22:32:03 2026
    From Newsgroup: comp.lang.fortran

    On Sat, 24 Oct 2026 13:26:07 -0700, Chris M. Thomasson wrote:

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

    On Fri, 23 Oct 2026 17:01:28 -0700, Chris M. Thomasson wrote:

    On 10/23/2026 3:42 PM, Lawrence DrCOOliveiro wrote:

    The whole aim of levels of abstraction is to tame the
    multi-headed beast of complexity that is computer programming.
    What you are doing here is breaking down those levels, all in the
    aid of, I donrCOt know, just to keep using gotos in your code, or
    something.

    Well, not about goto's and such. Just so a lib can inform the
    caller as to what it needs to work with. The caller sets it up,
    then calls into the init etc. Its being used in a lot of places.
    Take Vulkan.

    Where in Vulkan? Exposing implementation details to the caller not
    only increases complexity, it also limits the implementorrCOs ability
    to change those details later.

    Iiic, vkGetBufferMemoryRequirements and
    vkGetImageMemoryRequirements, which return a VkMemoryRequirements
    struct containing size, alignment, and memoryTypeBits. The caller
    allocates the memory with vkAllocateMemory and binds it with vkBindBufferMemory.

    I had a quick look at that. It seems to have to do with the reality of
    graphics hardware implementing different kinds of memory with
    different kinds of characteristics, and the impossibility of
    completely such ignoring such issues in real-time 3D rendering.

    I expect higher-level APIs (e.g. game engines) will wrap all this
    behind their own higher-level abstractions, so regular
    programmers/game creators donrCOt have to worry about it.

    In short, itrCOs an abstraction that leaks that you accept only because
    you have to, not because itrCOs a good idea for abstractions in general.
    If you can successfully hide issues of memory and other resource
    allocation behind your abstraction, you would still rather do it than
    not.

    So, to get back to my point, the technique I use is based on a form of structured programming called a rCLNassi-Shneiderman diagramrCY. The
    overall structure looks like

    ... initialize object pointer to NULL ...
    do /*once*/
    {
    ... possible other stuff ...
    ... allocate object pointer ...
    if (error occurred)
    break;
    ... possible other stuff using object pointer ...
    }
    while (false);
    ... call free(3) (or equivalent) on object pointer ...

    So you can see there is no way out of the inner block without passing
    through the dispose call. Using gotos would contribute nothing except
    make it harder to assure yourself of the simplicity of the control
    flow.

    Looks deceptively simple. But the same technique can scale up to quite
    complex cases.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 24 22:32:25 2026
    From Newsgroup: comp.lang.fortran

    On Sat, 24 Oct 2026 13:27:30 -0700, Chris M. Thomasson wrote:

    Or what about miniaudiorCOs ma_engine_get_heap_size plus ma_engine_init_preallocated

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

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

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

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

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

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

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

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

    Take your time...

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

    Please, take all the time you need to answer.

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

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

    - Dan C.


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    - Dan C.

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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

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

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

    (This statement remains true.)

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

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

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

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

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

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

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

    - Dan C.

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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

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



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

    - Dan C.


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

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

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

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

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

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

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

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

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

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

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

    There was also display postscript from SUN.

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

    On Sun, 25 Oct 2026 13:34:58 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote: >>On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]

    No, it isn't. How similar do you think the posix and windows threading >>model/api are? Yet somehow C++ provides a common wrapper for both. There is >>no reason the same can't be done for processes and your irrelevant waffle >>about past issues of threading on *nix don't change that.

    You didn't answer my questions.

    What do you think that a "thread" is?
    What do you think that a "process" is?

    Stop playing games - you don't get to answer a question with a question.
    Given I've been programming on unix for over 30 years and have written dozens of applications using multi process and multi threading and sometimes using both
    I'm quite well aware of the differences. Perhaps you arn't which is why you need me to tell you. Well go do your own research.

    In the meantime I'll ask one last time - why do you think C++ can provide
    a threading wrapper API but not a multi process one?

    Take your time.

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

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

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

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

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

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

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

    - Dan C.

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

    In article <11bl9qm$10h8f$1@dont-email.me>, <boltar@caprica.universe> wrote: >On Sun, 25 Oct 2026 13:34:58 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe> wrote: >>>On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]

    No, it isn't. How similar do you think the posix and windows threading >>>model/api are? Yet somehow C++ provides a common wrapper for both. There is >>>no reason the same can't be done for processes and your irrelevant waffle >>>about past issues of threading on *nix don't change that.

    You didn't answer my questions.

    What do you think that a "thread" is?
    What do you think that a "process" is?

    Stop playing games - you don't get to answer a question with a question.

    In other words, you don't know.

    Given I've been programming on unix for over 30 years and have written dozens >of applications using multi process and multi threading and sometimes using both
    I'm quite well aware of the differences. Perhaps you arn't which is why you >need me to tell you. Well go do your own research.

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

    In the meantime I'll ask one last time - why do you think C++ can provide
    a threading wrapper API but not a multi process one?

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

    Take your time.

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

    - Dan C.

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

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

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

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

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

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

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

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

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

    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: comp.lang.fortran

    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: comp.lang.fortran

    In article <11blaui$2q6vd$1@dont-email.me>, <boltar@caprica.universe> wrote: >On Sun, 25 Oct 2026 16:17:40 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]
    You didn't answer my questions.

    What do you think that a "thread" is?
    What do you think that a "process" is?

    Stop playing games - you don't get to answer a question
    with a question.

    In other words, you don't know.

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

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

    In the meantime I'll ask one last time - why do you think
    C++ can provide
    a threading wrapper API but not a multi process one?

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

    system?? ROTFL!! :)

    Oh dear, you really have no clue!

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

    Anyway, go ahead and keep flailing. Ta!

    - Dan C.

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

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

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

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

    - Dan C.

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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

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

    On 10/25/26 06:34, Dan Cross wrote:
    In article <11bkfcc$104cc$1@dont-email.me>,-a <boltar@caprica.universe> >>>> wrote:
    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]

    No, it isn't. How similar do you think the posix and windows threading >>>>> model/api are? Yet somehow C++ provides a common wrapper for both.
    There
    is
    no reason the same can't be done for processes and your irrelevant
    waffle
    about past issues of threading on *nix don't change that.

    You didn't answer my questions.

    What do you think that a "thread" is?
    What do you think that a "process" is?

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

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

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


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

    pt

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

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

    On 10/25/26 06:34, Dan Cross wrote:
    In article <11bkfcc$104cc$1@dont-email.me>, <boltar@caprica.universe>
    wrote:
    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]

    No, it isn't. How similar do you think the posix and windows threading >>>> model/api are? Yet somehow C++ provides a common wrapper for both. There >>>> is
    no reason the same can't be done for processes and your irrelevant waffle >>>> about past issues of threading on *nix don't change that.

    You didn't answer my questions.

    What do you think that a "thread" is?
    What do you think that a "process" is?

    - Dan C.

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

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


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

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

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

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

    On 10/25/26 06:34, Dan Cross wrote:
    In article <11bkfcc$104cc$1@dont-email.me>,-a <boltar@caprica.universe> >>>> wrote:
    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]

    No, it isn't. How similar do you think the posix and windows threading >>>>> model/api are? Yet somehow C++ provides a common wrapper for both.
    There
    is
    no reason the same can't be done for processes and your irrelevant
    waffle
    about past issues of threading on *nix don't change that.

    You didn't answer my questions.

    What do you think that a "thread" is?
    What do you think that a "process" is?

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

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

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


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

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

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

    On 10/25/26 06:34, Dan Cross wrote:
    In article <11bkfcc$104cc$1@dont-email.me>,-a <boltar@caprica.universe> >>>>> wrote:
    On Sun, 25 Oct 2026 00:28:19 -0000 (UTC)
    cross@spitfire.i.gajendra.net (Dan Cross) gabbled:
    [snip]

    No, it isn't. How similar do you think the posix and windows
    threading
    model/api are? Yet somehow C++ provides a common wrapper for both. >>>>>> There
    is
    no reason the same can't be done for processes and your irrelevant >>>>>> waffle
    about past issues of threading on *nix don't change that.

    You didn't answer my questions.

    What do you think that a "thread" is?
    What do you think that a "process" is?

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

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

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


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

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


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

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

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

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

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

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

    There was also display postscript from SUN.

    Display PostScript was from Adobe.

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

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

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

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

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

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

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

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

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

    Take your time...

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

    Please, take all the time you need to answer.

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

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

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


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

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






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

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

    snip

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

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

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


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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 14:36:44 2026
    From Newsgroup: comp.lang.fortran

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

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

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

    There was also display postscript from SUN.

    Display PostScript was from Adobe.

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

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

    Updating pixels on a computer screen? Use a frag shader.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

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

    On 10/22/2026 10:29 PM, Chris M. Thomasson wrote:
    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach if
    you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the
    caller?

    Have the caller have the object before hand and call a function to initialize it?

    Even analogous, to say, an API that says read n bytes and store into
    buffer. Well, the caller has lifetime of said buffer. The caller makes
    the buffer, calls into the function. The buffer bounds are known. Say a metadata stub:

    struct foobar_caller_alloc_helper
    {
    size_t m_size;
    size_t m_align;
    };




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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 00:42:55 2026
    From Newsgroup: comp.lang.fortran

    On Sun, 25 Oct 2026 16:16:26 -0700, Chris M. Thomasson wrote:

    Even analogous, to say, an API that says read n bytes and store into
    buffer. Well, the caller has lifetime of said buffer. The caller makes
    the buffer, calls into the function.

    So how is the caller supposed to manage that memory?
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:11:48 2026
    From Newsgroup: comp.lang.fortran

    On 10/25/2026 5:42 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 16:16:26 -0700, Chris M. Thomasson wrote:

    Even analogous, to say, an API that says read n bytes and store into
    buffer. Well, the caller has lifetime of said buffer. The caller makes
    the buffer, calls into the function.

    So how is the caller supposed to manage that memory?

    Ummm, say we wanted to have a buffer and use it.

    Say:

    {
    char buf[2048] = { '\0' };
    size_t bytes= foo_read(self, buf, 1024);
    }

    A caller provided buffer is normal with a lot of API's out there.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:21:00 2026
    From Newsgroup: comp.lang.fortran

    On 10/25/2026 5:42 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 16:16:26 -0700, Chris M. Thomasson wrote:

    Even analogous, to say, an API that says read n bytes and store into
    buffer. Well, the caller has lifetime of said buffer. The caller makes
    the buffer, calls into the function.

    So how is the caller supposed to manage that memory?

    Managing the memory is the callerrCOs job in C anyway. ThatrCOs the
    trade-off the language makes. read, recv, and mmap all work this way.
    This just applies the same contract to the librCOs own object.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Oct 25 19:28:00 2026
    From Newsgroup: comp.lang.fortran

    On 10/24/2026 3:32 PM, Lawrence DrCOOliveiro wrote:
    I had a quick look at that. It seems to have to do with the reality of graphics hardware implementing different kinds of memory with
    different kinds of characteristics, and the impossibility of
    completely such ignoring such issues in real-time 3D rendering.

    I expect higher-level APIs (e.g. game engines) will wrap all this
    behind their own higher-level abstractions, so regular
    programmers/game creators donrCOt have to worry about it.

    In short, itrCOs an abstraction that leaks that you accept only because
    you have to, not because itrCOs a good idea for abstractions in general.
    If you can successfully hide issues of memory and other resource
    allocation behind your abstraction, you would still rather do it than
    not.

    So, to get back to my point, the technique I use is based on a form of structured programming called a rCLNassi-Shneiderman diagramrCY. The
    overall structure looks like

    ... initialize object pointer to NULL ...
    do /*once*/
    {
    ... possible other stuff ...
    ... allocate object pointer ...
    if (error occurred)
    break;
    ... possible other stuff using object pointer ...
    }
    while (false);
    ... call free(3) (or equivalent) on object pointer ...

    So you can see there is no way out of the inner block without passing
    through the dispose call. Using gotos would contribute nothing except
    make it harder to assure yourself of the simplicity of the control
    flow.

    Looks deceptively simple. But the same technique can scale up to quite complex cases.


    The graphics case is where the leak is unavoidable, but thatrCOs not why
    IrCOd want it. A lib that never allocates behind your back is what you
    want in embedded, kernel, and arena code, and a foo_create wrapper on
    top gives you the hidden-allocation version for everyone else. Your
    do-once cleanup idiom works fine with it. You just call deinit and
    reclaim the block the way you made it. ItrCOs a way to structure the callerrCOs error handling, and it doesnrCOt say anything about who owns the memory.

    Say memory on a threads stack, no free needed.
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 03:39:38 2026
    From Newsgroup: comp.lang.fortran

    On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there.

    No it isnrCOt. ItrCOs not a good way to manage things, anyway: instead of solving the resource-allocation problem once and for all in the
    library API, you are pushing the burden onto all the client code, each
    one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 03:40:23 2026
    From Newsgroup: comp.lang.fortran

    On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote:

    Managing the memory is the callerrCOs job in C anyway.

    Does that apply to the caller of library APIs like malloc(3) and
    free(3)?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 03:43:05 2026
    From Newsgroup: comp.lang.fortran

    On Sun, 25 Oct 2026 19:28:00 -0700, Chris M. Thomasson wrote:

    A lib that never allocates behind your back is what you
    want in embedded, kernel, and arena code ...

    Even kernels want a common memory-management architecture, so addon
    modules donrCOt have to reinvent memory management on their own.

    Think of something like allocating low-priority cache memory, for
    stuff that can be dumped if necessary: that needs to be managed in the
    core of the kernel, so that if apps need regular memory for things
    they want to keep in memory, the kernel can free up cache as necessary
    to make more memory available.

    Stop trying to rationalize away the whole point of dynamic memory
    allocation.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 03:47:40 2026
    From Newsgroup: comp.lang.fortran

    On Sun, 25 Oct 2026 22:54:14 -0400, Cryptoengineer wrote:

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

    Interpreter for 16-bit integer arithmetic, according to <https://en.wikipedia.org/wiki/SWEET16>: ran at 1/10th the speed of
    native 6502 instructions, but took up just 300 bytes of RAM, but
    apparently cut the size of the whole Integer BASIC implementation by
    20%.
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

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

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

    You have low expectations then.

    Oh dear, you really have no clue!

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

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

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

    Anyway, go ahead and keep flailing. Ta!

    Go ahead and remain clueless.

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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

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

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

    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: comp.lang.fortran

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


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

    If you have to ask....

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

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

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

    Thats something else entirely.

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

    Not useless then, just less useful.

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

    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: comp.lang.fortran

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


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

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

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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

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

    On 10/25/2026 8:43 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:28:00 -0700, Chris M. Thomasson wrote:

    A lib that never allocates behind your back is what you
    want in embedded, kernel, and arena code ...

    Even kernels want a common memory-management architecture, so addon
    modules donrCOt have to reinvent memory management on their own.

    Think of something like allocating low-priority cache memory, for
    stuff that can be dumped if necessary: that needs to be managed in the
    core of the kernel, so that if apps need regular memory for things
    they want to keep in memory, the kernel can free up cache as necessary
    to make more memory available.

    Stop trying to rationalize away the whole point of dynamic memory
    allocation.

    If you need dynamic memory fine. If a lib allocates things for itself,
    fine. Just make sure to know how to clean it up. Also, the caller can
    use dynamic memory if it wants to. RAII is pretty nice here.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:26:38 2026
    From Newsgroup: comp.lang.fortran

    On 10/25/2026 8:39 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there.

    No it isnrCOt. ItrCOs not a good way to manage things, anyway: instead of solving the resource-allocation problem once and for all in the
    library API, you are pushing the burden onto all the client code, each
    one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:29:05 2026
    From Newsgroup: comp.lang.fortran

    On 10/25/2026 8:40 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote:

    Managing the memory is the callerrCOs job in C anyway.

    Does that apply to the caller of library APIs like malloc(3) and
    free(3)?

    Yes. The caller calls malloc, if it succeeded, the caller needs to free
    what it got... Right?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Harold Stevens@wookie@bookworm.localdomain to comp.lang.fortran on Mon Oct 26 15:31:10 2026
    From Newsgroup: comp.lang.fortran

    [froups trimmed to CLF]

    In <20261026220901.00005fbd@yahoo.com> Michael S:

    [Snip...]

    Your pretense that you know something about it is not o.k.
    In that regard you are not better than LDO.

    +1

    Extraordinarily adept thread-wreckers those two, Luke Skywalker.
    --
    Regards, Weird (Harold Stevens) * IMPORTANT EMAIL INFO FOLLOWS *
    Pardon any bogus email addresses (wookie) in place for spambots.
    Really, it's (wyrd) at att, dotted with net. * DO NOT SPAM IT. *
    I toss (404) GoogleGroup (404 http://twovoyagers.com/improve-usenet.org/).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 13:33:37 2026
    From Newsgroup: comp.lang.fortran

    On 10/26/2026 1:29 PM, Chris M. Thomasson wrote:
    On 10/25/2026 8:40 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote:

    Managing the memory is the callerrCOs job in C anyway.

    Does that apply to the caller of library APIs like malloc(3) and
    free(3)?

    Yes. The caller calls malloc, if it succeeded, the caller needs to free
    what it got... Right?

    Say a lib that has foo_create... Well, the damn called must remember to
    call foo_destroy, right?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 22:40:55 2026
    From Newsgroup: comp.lang.fortran

    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: comp.lang.fortran

    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 David Brown@david.brown@hesbynett.no to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 22:29:22 2026
    From Newsgroup: comp.lang.fortran

    On 26/10/2026 21:29, Chris M. Thomasson wrote:
    On 10/25/2026 8:40 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote:

    Managing the memory is the callerrCOs job in C anyway.

    Does that apply to the caller of library APIs like malloc(3) and
    free(3)?

    Yes. The caller calls malloc, if it succeeded, the caller needs to free
    what it got... Right?

    Exactly. The caller is responsible for /managing/ the memory (or it can
    pass on that responsibility to something else). malloc and free are
    provide and dispose of memory, they do not manage it.

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

    On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote:

    Say a lib that has foo_create... Well, the damn called must remember
    to call foo_destroy, right?

    Are you backpedalling from your previous idea that the caller must
    allocate the memory for the library to use?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 21:45:54 2026
    From Newsgroup: comp.lang.fortran

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

    HUH? How do you call say, fread without a user provided buffer?

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

    On Mon, 26 Oct 2026 13:23:59 -0700, Chris M. Thomasson wrote:

    If you need dynamic memory fine.

    What the hell do you think we have been talking about this whole
    time??
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 14:47:07 2026
    From Newsgroup: comp.lang.fortran

    On 10/26/2026 2:45 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote:

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    Ummm... What we were talking about. You snipped a lot. See, the caller
    needs to have the buffer in order to call fread, right?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 14:51:57 2026
    From Newsgroup: comp.lang.fortran

    On 10/26/2026 2:46 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:23:59 -0700, Chris M. Thomasson wrote:

    If you need dynamic memory fine.

    What the hell do you think we have been talking about this whole
    time??

    Why do you "seem" to think we "always" need dynamic memory? Then you ask
    this gem:
    __________
    Does that apply to the caller of library APIs like malloc(3) and
    free(3)?
    __________

    See, the caller is responsible for managing things. Say foo_create that succeeds. Well, now the caller must call foo_destroy.


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

    On 10/26/2026 2:45 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote:

    Say a lib that has foo_create... Well, the damn called must remember
    to call foo_destroy, right?

    Are you backpedalling from your previous idea that the caller must
    allocate the memory for the library to use?

    Where did I say must? I said some libs allow the caller to create their internal state. You are the one that seems to not understand it? Either
    way, the caller needs to manage things in C. malloc/free, etc.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 14:58:35 2026
    From Newsgroup: comp.lang.fortran

    On 10/26/2026 2:29 PM, David Brown wrote:
    On 26/10/2026 21:29, Chris M. Thomasson wrote:
    On 10/25/2026 8:40 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote:

    Managing the memory is the callerrCOs job in C anyway.

    Does that apply to the caller of library APIs like malloc(3) and
    free(3)?

    Yes. The caller calls malloc, if it succeeded, the caller needs to
    free what it got... Right?

    Exactly.-a The caller is responsible for /managing/ the memory (or it can pass on that responsibility to something else).-a malloc and free are provide and dispose of memory, they do not manage it.


    Right. For instance take my ralloc thing. A user can create a big pile
    of memory, have rallocex carve it up for them (align, etc), and use it.
    But, the user needs to know how to free that memory. If its on the
    stack, well, easy. If not call free, or whatever it needs.

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

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

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

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

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

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

    Like it or not, the Unix model has conquered the world.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lynn 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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 22:20:23 2026
    From Newsgroup: comp.lang.fortran

    On Mon, 26 Oct 2026 14:53:48 -0700, Chris M. Thomasson wrote:

    On 10/26/2026 2:45 PM, Lawrence DrCOOliveiro wrote:

    On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote:

    Say a lib that has foo_create... Well, the damn called must
    remember to call foo_destroy, right?

    Are you backpedalling from your previous idea that the caller must
    allocate the memory for the library to use?

    Where did I say must?

    You said rCLManaging the memory is the callerrCOs job in C anyway.rCY You didnrCOt say rCLcould be the callerrCOs jobrCY as in rCLthe caller could have a choicerCY, you said rCL*is* the callerrCOs jobrCY. No choice. I.e. the caller *must* manage memory.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 15:42:31 2026
    From Newsgroup: comp.lang.fortran

    On 10/26/2026 3:20 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 14:53:48 -0700, Chris M. Thomasson wrote:

    On 10/26/2026 2:45 PM, Lawrence DrCOOliveiro wrote:

    On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote:

    Say a lib that has foo_create... Well, the damn called must
    remember to call foo_destroy, right?

    Are you backpedalling from your previous idea that the caller must
    allocate the memory for the library to use?

    Where did I say must?

    You said rCLManaging the memory is the callerrCOs job in C anyway.rCY You didnrCOt say rCLcould be the callerrCOs jobrCY as in rCLthe caller could have a
    choicerCY, you said rCL*is* the callerrCOs jobrCY. No choice. I.e. the caller *must* manage memory.

    But, the caller must take care in C. Say a lib that allows the caller to create their own memory from the requirements reaped from the lib. Okay.
    Fine. Also, take a lib that is more "encapsulated" than say a pure foo_create/destroy. The caller must remember to call foo_destroy, right?

    Using io_uring is a fun one. The caller created the memory, iirc from
    mmap, so the kernel can use it. The Kernel punts off the lifetime
    management of the users ring buffers.

    The C must manage things regardless. say malloc and free?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 15:46:04 2026
    From Newsgroup: comp.lang.fortran

    On 10/25/2026 8:40 PM, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:21:00 -0700, Chris M. Thomasson wrote:

    Managing the memory is the callerrCOs job in C anyway.

    Does that apply to the caller of library APIs like malloc(3) and
    free(3)?

    you should print that out and frame it.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 16:06:08 2026
    From Newsgroup: comp.lang.fortran

    On 10/26/2026 3:20 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 14:53:48 -0700, Chris M. Thomasson wrote:

    On 10/26/2026 2:45 PM, Lawrence DrCOOliveiro wrote:

    On Mon, 26 Oct 2026 13:33:37 -0700, Chris M. Thomasson wrote:

    Say a lib that has foo_create... Well, the damn called must
    remember to call foo_destroy, right?

    Are you backpedalling from your previous idea that the caller must
    allocate the memory for the library to use?

    Where did I say must?

    You said rCLManaging the memory is the callerrCOs job in C anyway.rCY You didnrCOt say rCLcould be the callerrCOs jobrCY as in rCLthe caller could have a
    choicerCY, you said rCL*is* the callerrCOs jobrCY. No choice. I.e. the caller *must* manage memory.

    A simple pattern... Now, some libs can do it others are simply not
    designed that way.


    foo_alloc_req r = foo_query_alloc(&cfg);
    void *mem = aligned_alloc(r.align, r.size); /* once */

    for (int i = 0; i < n_jobs; ++i) {
    foo *f = foo_init(mem, r.size, &cfg); /* build in the same
    block */
    /* ... use f ... */
    foo_deinit(f); /* object ends, block
    stays ours */
    }

    free(mem); /* once, at the very end */ --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lars Poulsen@lars@beagle-ears.com to comp.lang.fortran,comp.lang.c++,alt.folklore.computers on Mon Oct 26 19:14:57 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

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

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

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

    But if you hotheads can't agree on that, can you please now agree to
    disagree and shut up!
    --
    Lars Poulsen - an old geek in Santa Barbara, California
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to 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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 19:29:29 2026
    From Newsgroup: comp.lang.fortran

    On 10/24/2026 3:43 AM, David Brown wrote:
    On 23/10/2026 18:57, Peter Flass wrote:
    On 10/23/26 02:45, David Brown wrote:
    On 23/10/2026 08:25, Lawrence DrCOOliveiro wrote:
    On Thu, 22 Oct 2026 22:29:45 -0700, Chris M. Thomasson wrote:

    On 10/22/2026 8:19 PM, Lawrence DrCOOliveiro wrote:

    On Thu, 22 Oct 2026 07:26:21 -0700, Peter Flass wrote:

    That's why I try to use PL/I AUTOMATIC (stack) storage and not
    allocate a lot of stuff. You need to have a disciplined approach >>>>>>> if you allocate random stuff here and there.

    What if yourCOre building an object that needs to be returned to the >>>>>> caller?

    Have the caller have the object before hand and call a function to
    initialize it?

    IrCOm assuming that all that BASIC programming hasnrCOt got to your head, >>>> and yourCOre not serious. ;)

    Chris' wording is perhaps poor, but the principle is right.

    I don't know PL/I or Fortran, but in C if you have :

    -a-a-a-a-atypedef struct data_struct { int a; int xs[20]; } S ;

    -a-a-a-a-aS build_some_data(void) {
    -a-a-a-a-a-a-a-a S s;

    -a-a-a-a-a-a-a-a s.a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) s.xs[i] = i;

    -a-a-a-a-a-a-a-a return s;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s = build_some_data();
    -a-a-a-a-a}


    then it is typically handled as though you had written :

    -a-a-a-a-avoid build_some_data(S * p) {
    -a-a-a-a-a-a-a-a p->a = 123;
    -a-a-a-a-a-a-a-a for (int i = 0; i < 20; i++) p->xs[i] = i;

    -a-a-a-a-a-a-a-a return;
    -a-a-a-a-a}

    -a-a-a-a-avoid foo() {
    -a-a-a-a-a-a-a-a S s;
    -a-a-a-a-a-a-a-a build_some_data(&s);
    -a-a-a-a-a}


    That is - the caller creates the /space/ for the returned object, but
    does not do any kind of initialisation.-a It passes a pointer to that
    space as a hidden parameter to the function that wants to return the
    object.

    That principle should work fine in any language, as long as the size
    of the returned object is known by the caller code.

    That last sentence is why it would not work fine,

    OK.-a Knowing the size of the returned object is an absolute requirement
    for pre-allocation by the caller, and it is a requirement that is fine
    for a lot of situations and a lot of languages.-a But if it is not the
    case for PL/I, Fortran, or any other particular language (or particular function in any language), then I fully agree - the object's space can't
    be handled by the caller.


    Use when the API provides it, or else, well, read the api learn and know
    how to use it. If it allows the caller to make the memory it needs, so
    be it, if not, who cares?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 19:43:04 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

    IrCOm having trouble with the disk.

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

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

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

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

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

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

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

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

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


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

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

    I was in the linux world for a whiel, along with solaris, etc. But
    Windows, oh my. vcpkg is a big turn.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 19:57:22 2026
    From Newsgroup: comp.lang.fortran

    On 10/24/2026 3:32 PM, Lawrence DrCOOliveiro wrote:
    On Sat, 24 Oct 2026 13:27:30 -0700, Chris M. Thomasson wrote:

    Or what about miniaudiorCOs ma_engine_get_heap_size plus
    ma_engine_init_preallocated

    No idea about that, but the same principle would apply.

    You sound like you never worked with any of it before?????
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Oct 26 20:09:48 2026
    From Newsgroup: comp.lang.fortran

    On 10/24/2026 3:32 PM, Lawrence DrCOOliveiro wrote:
    On Sat, 24 Oct 2026 13:27:30 -0700, Chris M. Thomasson wrote:

    Or what about miniaudiorCOs ma_engine_get_heap_size plus
    ma_engine_init_preallocated

    No idea about that, but the same principle would apply.

    Sure you do, or what are you writing about anyway? Really?

    You seem like the oracle, right?
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 05:56:28 2026
    From Newsgroup: comp.lang.fortran

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

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

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

    Keeping them up to date is, afaict, manual.

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

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

    Example from my system:

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

    Where did these come from?

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    <https://manpages.debian.org/clone(2)> is the underlying common kernel
    call that is used to implement both fork(2) and pthread_create(3) on
    Linux.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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: comp.lang.fortran

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

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

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

    aaaaaint x;

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

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

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

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

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

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

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

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

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

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

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

    - Dan C.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From James Kuyper@jameskuyper@alumni.caltech.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 11:00:08 2026
    From Newsgroup: comp.lang.fortran

    On 2026-10-26 17:45, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote:
    [restore snippage]>> On 2026-10-25 23:39, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there.

    No it isnrCOt. ItrCOs not a good way to manage things, anyway: instead of >>> solving the resource-allocation problem once and for all in the
    library API, you are pushing the burden onto all the client code, each
    one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    fread() uses a caller-provided buffer, which, according to your previous comment, "push[es] the burden onto all the client code, each one of
    which has to solve it for itself", so according to you, "That's a dumb
    way to design things"..If that isn't your actual opinion of fread(),
    your comments need to be at least a little more nuanced to avoid
    applying to fread().
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 15:03:45 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

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

    Unisys released the OS as part of their massively parallel
    OPUS computer system.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 09:41:16 2026
    From Newsgroup: comp.lang.fortran

    On 10/27/26 08:00, James Kuyper wrote:
    On 2026-10-26 17:45, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote:
    [restore snippage]>> On 2026-10-25 23:39, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there.

    No it isnrCOt. ItrCOs not a good way to manage things, anyway: instead of >>>> solving the resource-allocation problem once and for all in the
    library API, you are pushing the burden onto all the client code, each >>>> one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    fread() uses a caller-provided buffer, which, according to your previous comment, "push[es] the burden onto all the client code, each one of
    which has to solve it for itself", so according to you, "That's a dumb
    way to design things"..If that isn't your actual opinion of fread(),
    your comments need to be at least a little more nuanced to avoid
    applying to fread().

    The difference is that the size of the buffer for fread() is the maximum
    you want/expect to read. The size of an object is the size it is, not necessarily what you expect. If you don't provide enough space you will truncate.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From scott@scott@slp53.sl.home (Scott Lurndal) to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 18:36:48 2026
    From Newsgroup: comp.lang.fortran

    Peter Flass <Peter@Iron-Spring.com> writes:
    On 10/27/26 08:00, James Kuyper wrote:
    On 2026-10-26 17:45, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote:
    [restore snippage]>> On 2026-10-25 23:39, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there.

    No it isnrCOt. ItrCOs not a good way to manage things, anyway: instead of >>>>> solving the resource-allocation problem once and for all in the
    library API, you are pushing the burden onto all the client code, each >>>>> one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    fread() uses a caller-provided buffer, which, according to your previous
    comment, "push[es] the burden onto all the client code, each one of
    which has to solve it for itself", so according to you, "That's a dumb
    way to design things"..If that isn't your actual opinion of fread(),
    your comments need to be at least a little more nuanced to avoid
    applying to fread().

    The difference is that the size of the buffer for fread() is the maximum
    you want/expect to read. The size of an object is the size it is, not >necessarily what you expect. If you don't provide enough space you will >truncate.

    Which isn't a significant issue with fread, since the underlying stdio
    buffer (or kernel file cache or terminal driver buffer) will hold the
    unread information for the next call to fread.

    fread(3) is basically obsolete for most high-performance applications
    which map the file directly into the process address space (mmap).
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 22:22:12 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 27 Oct 2026 11:00:08 -0400, James Kuyper wrote:

    On 2026-10-26 17:45, Lawrence DrCOOliveiro wrote:

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

    On 2026-10-25 23:39, Lawrence DrCOOliveiro wrote:

    On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there.

    No it isnrCOt. ItrCOs not a good way to manage things, anyway:
    instead of solving the resource-allocation problem once and for
    all in the library API, you are pushing the burden onto all the
    client code, each one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    fread() uses a caller-provided buffer, which, according to your previous comment, "push[es] the burden onto all the client code, each one of
    which has to solve it for itself", so according to you, "That's a dumb
    way to design things"..

    Not even paying attention to whatrCOs being said in the parts you
    quoted, never mind the parts you didnrCOt. Note my remark above about rCLsolving the resource allocation problemrCY; elsewhere I asked: rCLWhat if yourCOre building an object that needs to be returned to the caller?rCY

    Not clear yet what werCOre talking about here? WerCOre not talking about
    random API calls, werCOre talking about libraries that need to create
    and manage abstract objects that encapsulate the function they are
    providing!
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From James Kuyper@jameskuyper@alumni.caltech.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 21:35:09 2026
    From Newsgroup: comp.lang.fortran

    Thanks to my killfile, I don't see messages posted by Chris M.
    Thomasson, just other people's responses to them.

    On 2026-10-25 20:42, Lawrence DrCOOliveiro wrote:
    On Sun, 25 Oct 2026 16:16:26 -0700, Chris M. Thomasson wrote:

    Even analogous, to say, an API that says read n bytes and store into
    buffer. Well, the caller has lifetime of said buffer. The caller makes
    the buffer, calls into the function.

    So how is the caller supposed to manage that memory?

    That's the oldest message I can find on this sub-thread, and also the
    very last message I can find preceding the one quoted below, and it's
    clearly describing an fread()-like interface, not a function that
    returns objects of sizes unknown to the caller. If the messages I don't
    see gave some other context to this sub-thread, I had no way of knowing
    about it.

    On 2026-10-27 18:22, Lawrence DrCOOliveiro wrote:
    On Tue, 27 Oct 2026 11:00:08 -0400, James Kuyper wrote:

    On 2026-10-26 17:45, Lawrence DrCOOliveiro wrote:

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

    On 2026-10-25 23:39, Lawrence DrCOOliveiro wrote:

    On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there.

    No it isnrCOt. ItrCOs not a good way to manage things, anyway:
    instead of solving the resource-allocation problem once and for
    all in the library API, you are pushing the burden onto all the
    client code, each one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    fread() uses a caller-provided buffer, which, according to your previous
    comment, "push[es] the burden onto all the client code, each one of
    which has to solve it for itself", so according to you, "That's a dumb
    way to design things"..

    Not even paying attention to whatrCOs being said in the parts you
    quoted, never mind the parts you didnrCOt. Note my remark above about rCLsolving the resource allocation problemrCY; elsewhere I asked: rCLWhat if yourCOre building an object that needs to be returned to the caller?rCY

    Yes, and without the context that applies elsewhere, your comment about resource allocation comes off as a non-sequitur.
    Not clear yet what werCOre talking about here? WerCOre not talking about random API calls, werCOre talking about libraries that need to create
    and manage abstract objects that encapsulate the function they are
    providing!

    I can find no mention of that topic anywhere on this sub-thread. It
    might be in the parts of Chris's messages that I didn't see and you
    didn't quote.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 01:43:55 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote:

    ... without the context that applies elsewhere, your comment about
    resource allocation comes off as a non-sequitur.

    ThatrCOs just an excuse. Other comments of mine, from further back in
    this particular line of this thread:

    * rCLWhat if yourCOre building an object that needs to be returned to the
    caller?rCY
    * rCLThe principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.rCY
    * rCLIf you have to do cleanup at each level before exiting, then it works
    perfectly well.rCY

    Did you notice any of that?

    From elsewhere in the discussion:

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error
    recovery will invariably involve cleaning up those parts of the
    allocations which already succeeded. Gotos are no good for this;
    you need to exit levels of structure nesting one by one, disposing
    of allocations as you go.

    I put together an example here
    <https://gitlab.com/ldo/a_structured_discipline_of_programming>.
    This is an extension module that offers services to Python code,
    because that is just about the worst example I could think of, for
    those who think gotos can cut it.

    Did you pay attention to any of that?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From James Kuyper@jameskuyper@alumni.caltech.edu to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 22:18:54 2026
    From Newsgroup: comp.lang.fortran

    On 2026-10-27 21:43, Lawrence DrCOOliveiro wrote:
    On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote:

    ... without the context that applies elsewhere, your comment about
    resource allocation comes off as a non-sequitur.

    ThatrCOs just an excuse. Other comments of mine, from further back in
    this particular line of this thread:

    * rCLWhat if yourCOre building an object that needs to be returned to the
    caller?rCY
    * rCLThe principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.rCY
    * rCLIf you have to do cleanup at each level before exiting, then it works
    perfectly well.rCY

    Did you notice any of that?
    No, none of those comments appear anywhere in this sub-thread as
    displayed by Thunderbird. How do they fit in to the sequence of messages
    that lead to this one? If they appeared in some other sub-thread, that's
    not relevant; the fact that something is being discussed in another
    sub-thread doesn't make it relevant to what's being discussed in this
    one. However, if those comments occur in Chris' text that I never saw,
    or in messages on this sub-thread that are prior to the earliest one I
    quoted, then they would be relevant.
    The references for the oldest message I quoted indicate that there were
    20 previous ones in that sub-thread, but they don't display as
    predecessors of that message. This is a common problem when I filter out
    all the messages posted by someone. If that person is a significant
    contributor to a particular thread, that thread gets chopped up into
    pieces and Thunderbird fails to notice that those pieces are related to
    each other.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Peter Flass@Peter@Iron-Spring.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Oct 27 19:28:47 2026
    From Newsgroup: comp.lang.fortran

    On 10/27/26 18:43, Lawrence DrCOOliveiro wrote:
    On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote:

    ... without the context that applies elsewhere, your comment about
    resource allocation comes off as a non-sequitur.

    ThatrCOs just an excuse. Other comments of mine, from further back in
    this particular line of this thread:

    * rCLWhat if yourCOre building an object that needs to be returned to the
    caller?rCY
    * rCLThe principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.rCY
    * rCLIf you have to do cleanup at each level before exiting, then it works
    perfectly well.rCY

    Did you notice any of that?

    From elsewhere in the discussion:

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error
    recovery will invariably involve cleaning up those parts of the
    allocations which already succeeded. Gotos are no good for this;
    you need to exit levels of structure nesting one by one, disposing
    of allocations as you go.

    I put together an example here
    <https://gitlab.com/ldo/a_structured_discipline_of_programming>.
    This is an extension module that offers services to Python code,
    because that is just about the worst example I could think of, for
    those who think gotos can cut it.

    Did you pay attention to any of that?

    You could keep track of the allocations in a list (or whatever) and then
    walk thru and clean them up at once.

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

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


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

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

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

    Thats your problem, not mine.

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

    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: comp.lang.fortran

    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: comp.lang.fortran

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



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

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

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

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


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

    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: comp.lang.fortran

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


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

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

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

    Thats your problem, not mine.

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

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


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

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

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

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

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



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

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

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

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

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

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

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

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


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

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





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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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 Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Oct 28 14:16:43 2026
    From Newsgroup: comp.lang.fortran

    On 10/27/2026 6:43 PM, Lawrence DrCOOliveiro wrote:
    On Tue, 27 Oct 2026 21:35:09 -0400, James Kuyper wrote:

    ... without the context that applies elsewhere, your comment about
    resource allocation comes off as a non-sequitur.

    ThatrCOs just an excuse. Other comments of mine, from further back in
    this particular line of this thread:

    * rCLWhat if yourCOre building an object that needs to be returned to the
    caller?rCY
    * rCLThe principle applies to Fortran as it does to any language where
    you have to explicitly manage storage allocations.rCY
    * rCLIf you have to do cleanup at each level before exiting, then it works
    perfectly well.rCY

    Did you notice any of that?

    From elsewhere in the discussion:

    I find the C code I write tends to do a lot of dynamic resource
    allocations. These can sometimes fail with errors. So error
    recovery will invariably involve cleaning up those parts of the
    allocations which already succeeded. Gotos are no good for this;
    you need to exit levels of structure nesting one by one, disposing
    of allocations as you go.

    I put together an example here
    <https://gitlab.com/ldo/a_structured_discipline_of_programming>.
    This is an extension module that offers services to Python code,
    because that is just about the worst example I could think of, for
    those who think gotos can cut it.

    Did you pay attention to any of that?

    Its actually pretty simple. There are libs out there that allow the
    caller to create the memory it needs. io_uring is just one of them.

    DirectX12 is another. The user creates all the memory, aligns it, etc,
    and can update a single frame with a single memcpy.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to rec.arts.sf.written,comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Thu Oct 29 00:06:45 2026
    From Newsgroup: comp.lang.fortran

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

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

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


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

    If you have to ask....

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

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

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


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

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






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

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

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

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


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

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

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


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

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

    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: comp.lang.fortran

    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: comp.lang.fortran

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

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


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

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

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


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


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

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

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

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

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

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

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

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

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



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

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

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

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

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

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



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

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


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

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

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

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

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



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

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

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

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

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

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



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

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


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

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


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



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

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

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


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

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

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


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

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

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

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

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

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

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

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

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

    - Dan C.

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

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

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

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



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

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

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

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

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

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



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

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


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

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


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

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

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

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

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

    - Dan C.

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

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


    What's the situation re C++ 26?

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

    Any progress?




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

    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: comp.lang.fortran

    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: comp.lang.fortran

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

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

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

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


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

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

    What happens when caller is GUI-style application?

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

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

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

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

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

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

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

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

    - Dan C.

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

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

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

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

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


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

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

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


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

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

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

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


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


    Good to know.

    nor will the shell itself.

    That part I guessed myself.

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

    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: comp.lang.fortran

    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: comp.lang.fortran

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

    What happens when caller is GUI-style application?

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

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


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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

    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 boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 09:45:04 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 30 Oct 2026 22:35:05 -0000 (UTC)
    Lawrence =?iso-8859-13?q?D=FFOliveiro?= <ldo@nz.invalid> gabbled:
    The trend nowadays is to revive the old coroutine concept, in a new
    guise called rCLstacklessrCY coroutines. These give you support for async >operations, but with transfers of control being made explicit at
    rCLawaitrCY points, rather than unpredictably as with full preemptive >threading. This greatly reduces the opportunity for race conditions.

    Coroutines are just a complicated way to re-implement a function with a load
    of statics.

    eg:

    void myfunc()
    {
    static int i = 0;
    for(;;++i)
    {
    [do something based on value of i]
    [return when some condition met]
    }
    }

    Also the C++ implementation is so bad its unusable.

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

    Python nailed it - you just call "yield", job done.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sat Oct 31 09:47:42 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 08:32:42 2026
    From Newsgroup: comp.lang.fortran

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

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

    On what planet?

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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 19:40:08 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

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

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

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

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

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

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

    On what planet?

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


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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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 Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Sun Nov 1 23:38:32 2026
    From Newsgroup: comp.lang.fortran

    Anyway, to get the discussion back on track:

    I put together an example here <https://gitlab.com/ldo/a_structured_discipline_of_programming>. This
    is an extension module that offers services to Python code, because
    that is just about the worst example I could think of, for those who
    think gotos can cut it.

    Problems I am trying to address:

    * Leaking memory: allocating something and forgetting to dispose of
    it
    * Double-free: the opposite problem, trying to free a memory block
    that has already been freed

    The basic structured-programming pattern I follow is:

    1: Initialize a pointer variable to `NULL`
    2: Allocate memory for the pointer (this might fail)
    3: Correctly free the pointer memory, regardless of allocation
    success/failure

    This project uses the implementation of a Python extension module as a
    specific example, since Python itself is a highly dynamic language,
    and so code that is written in a lower-level-language like C for
    interfacing to Python typically has to deal a lot with allocation and management of Python objects and other dynamic memory.

    In more concrete terms, the code pattern looks like this:

    PyObject * obj = NULL; /* step 1 */
    do /*once*/
    {
    ... possible other stuff ...
    allocate obj; /* step 2 */
    if (PyErr_Occurred())
    break;
    ... possible other stuff using obj ...
    }
    while (false);
    Py_XDECREF(obj); /* step 3 */

    Assuming there are no `goto`s in the rCL...rCY parts (or `return`
    statements, or shenanigans like `setjmp`(3)/`longjmp`(3)), it should
    be clear that, regardless of what happens in those parts (provided
    they donrCOt free or reallocate `obj`), any memory allocated to `obj`
    will be correctly freed.

    Key to this pattern is the fact that `Py_XDECREF` is a noop (and
    raises no error) if it is passed a `NULL` pointer. This is also the
    semantics of the `free`(3) routine in the C standard library, and I
    recommend that any memory-disposal routine you create implement the
    same behaviour. It saves checking for unallocated storage in the
    cleanup code: just unconditionally dispose of everything temporary
    that might have been allocated.

    The above basic structure scales easily. For example, coping with
    multiple objects needing allocating:

    PyObject * obj1 = NULL;
    PyObject * obj2 = NULL;
    do /*once*/
    {
    ... possible other stuff ...
    allocate obj1;
    if (PyErr_Occurred())
    break;
    ... possible other stuff using obj1 ...
    allocate obj2;
    if (PyErr_Occurred())
    break;
    ... possible other stuff using obj1 and obj2 ...
    }
    while (false);
    Py_XDECREF(obj1);
    Py_XDECREF(obj2);

    Nested blocks:

    PyObject * obj1 = NULL;
    do /*once*/
    {
    ... possible other stuff ...
    allocate obj1;
    if (PyErr_Occurred())
    break;
    ... possible other stuff using obj1 ...
    {
    PyObject * obj2 = NULL;
    do /*once*/
    {
    ... even more possible stuff using obj1 ...
    allocate obj2;
    if (PyErr_Occurred())
    break;
    ... possible other stuff using obj1 and obj2 ...
    }
    while (false);
    Py_XDECREF(obj2);
    }
    if (PyErr_Occurred())
    break;
    ... yet more possible stuff using obj1 ...
    }
    while (false);
    Py_XDECREF(obj1);

    Allocation within loops:

    for (ssize_t i = 0;;)
    {
    if (i == nr_items)
    break;
    PyObject * const item = PyTuple_GetItem(items, i);
    if (item == NULL)
    break;
    {
    PyObject * key = NULL;
    PyObject * value = NULL;
    do /*once*/
    {
    ... construct key ...
    if (PyErr_Occurred())
    break;
    ... construct value ...
    if (PyErr_Occurred())
    break;
    if (PyDict_SetItem(tempresult, key, value) < 0)
    break;
    }
    while (false);
    Py_XDECREF(key);
    Py_XDECREF(value);
    }
    if (PyErr_Occurred())
    break;
    ++i;
    } /*for*/
    if (PyErr_Occurred())
    break;

    Etc, etc.
    --- 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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 10:54:42 2026
    From Newsgroup: comp.lang.fortran

    On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is

    the win for comment it is when code explain itself with 0 comment
    --- 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: comp.lang.fortran

    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 Fred. Zwarts@F.Zwarts@HetNet.nl to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 11:11:40 2026
    From Newsgroup: comp.lang.fortran

    Op 02.nov.2026 om 10:54 schreef Rosario19:
    On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is

    the win for comment it is when code explain itself with 0 comment

    Code can only explain what it does, what the algorithm is.
    Code cannot explain why that algorithm was chosen. That is where
    comments are for.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 15:43:42 2026
    From Newsgroup: comp.lang.fortran

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


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

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

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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: comp.lang.fortran

    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 Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 16:51:46 2026
    From Newsgroup: comp.lang.fortran

    On 2026-11-02, Fred. Zwarts <F.Zwarts@HetNet.nl> wrote:

    Op 02.nov.2026 om 10:54 schreef Rosario19:

    On Tue, 20 Oct 2026 20:20:39 -0000 (UTC), Lawrence D|+Oliveiro wrote:

    On Tue, 20 Oct 2026 15:06:48 -0500, Lynn McGuire wrote:

    The key to writing any software is lots of commenting.

    A key point about comments is they should explain *why* the code is

    the win for comment it is when code explain itself with 0 comment

    Code can only explain what it does, what the algorithm is.
    Code cannot explain why that algorithm was chosen. That is where
    comments are for.

    Unfortuately, a lot of people (especially CS weenies) love to
    loudly proclaim, "My code is so readable that no comments are
    necessary!" (Sometimes they apply this argument to their choice
    of programming language as well.) They're usually wrong.
    --
    /~\ 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 Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 16:51:47 2026
    From Newsgroup: comp.lang.fortran

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

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

    Michael S <already5chosen@yahoo.com> gabbled:

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

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

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

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

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

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

    On Mon, 02 Nov 2026 16:51:46 GMT, Charlie Gibbs wrote:

    Unfortuately, a lot of people (especially CS weenies) love to loudly proclaim, "My code is so readable that no comments are necessary!"

    WasnrCOt that the argument made by the rCLbusinessrCY users for COBOL? That
    the language was practically English anyway ... ?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 23:46:58 2026
    From Newsgroup: comp.lang.fortran

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

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


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

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


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

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


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to 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: comp.lang.fortran

    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: comp.lang.fortran

    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: comp.lang.fortran

    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 comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 14:59:26 2026
    From Newsgroup: comp.lang.fortran

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

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

    On what planet?

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


    Either you are trolling or don't have a clue?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 15:00:03 2026
    From Newsgroup: comp.lang.fortran

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


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

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


    Ever use Nt say 4.0? IOCP?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 15:02:44 2026
    From Newsgroup: comp.lang.fortran

    On 11/2/2026 1:46 PM, Michael S wrote:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

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


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

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


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

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



    Well, before IOCP we would need to use WaitForMultipleObjects, iirc. But
    there was a trick we had to use. We had to alter the indices! Shift
    them, or even randomize them.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 15:03:44 2026
    From Newsgroup: comp.lang.fortran

    On 11/2/2026 1:46 PM, Michael S wrote:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

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


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

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


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

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



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

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

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

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

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

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

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

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

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


    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Nov 3 02:42:44 2026
    From Newsgroup: comp.lang.fortran

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

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

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

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 21:09:02 2026
    From Newsgroup: comp.lang.fortran

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:
    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

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

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.


    Well, on Linux we have aio or io_uring. The latter is more low level
    than the Windows IOCP.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Mon Nov 2 21:11:05 2026
    From Newsgroup: comp.lang.fortran

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:
    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote:

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

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

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.


    These are for high performance systems. But, they solve a lot of
    problems. Say your program starts to gain a lot of users?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Charlie Gibbs@cgibbs@kltpzyxm.invalid to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Nov 3 07:15:06 2026
    From Newsgroup: comp.lang.fortran

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

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:

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

    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

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

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.

    These are for high performance systems. But, they solve a lot of
    problems. Say your program starts to gain a lot of users?

    In our environment that should never happen. The only legitimate
    users are those that are other elements of our software package.
    Any others (or too many seemingly legitimate users) get a rejection
    message, followed by disconnection.
    --
    /~\ Charlie Gibbs | In this world there are
    \ / <cgibbs@kltpzyxm.invalid> | two kinds of people:
    X I'm really at ac.dekanfrus | 1. Those who can extrapolate
    / \ if you read it the right way. | from incomplete data.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Nov 3 21:51:42 2026
    From Newsgroup: comp.lang.fortran

    On Mon, 2 Nov 2026 15:03:44 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote:

    On 11/2/2026 1:46 PM, Michael S wrote:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

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


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

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


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

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



    Have you ever used IOCP on windows?

    No, I didn't.
    IMHO, IO compleiion ports "solve" problems that do not exist today
    and mostly did not exist since 15-20 years ago.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Tue Nov 3 13:10:09 2026
    From Newsgroup: comp.lang.fortran

    On 11/3/2026 11:51 AM, Michael S wrote:
    On Mon, 2 Nov 2026 15:03:44 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> wrote:

    On 11/2/2026 1:46 PM, Michael S wrote:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:

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


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

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


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

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



    Have you ever used IOCP on windows?

    No, I didn't.
    IMHO, IO compleiion ports "solve" problems that do not exist today
    and mostly did not exist since 15-20 years ago.


    Are you suggesting that IOCP is useless? What about AIO or io_uring? AIO
    is basically IOCP anyway. io_uring is special, but still uses a
    "completion" setup.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:48:49 2026
    From Newsgroup: comp.lang.fortran

    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

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

    Michael S <already5chosen@yahoo.com> gabbled:

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

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

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

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


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

    No I don't mean that and I can't be bother explaining what multiplexing means to someone who's clearly never used it.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:54:20 2026
    From Newsgroup: comp.lang.fortran

    On Mon, 2 Nov 2026 23:46:58 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Mon, 2 Nov 2026 15:43:42 -0000 (UTC)
    boltar@caprica.universe wrote:
    Last time I had the misfortune to use win32 it couldn't multiplex on
    sockets.


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

    Yes, for some bizarre reason MS implemented the userspace sockets as some
    kind of handle instead of an integer file descriptor like every other sockets library.

    2) today, with nearly all file I/O deeply cached, multiplexing waiting
    for file I/O with waiting for sockets is a bad idea. OTOH, Multiplexing >sockets with pipes could still make sense, infrequently.

    Depends on the use case.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 08:54:51 2026
    From Newsgroup: comp.lang.fortran

    On Mon, 2 Nov 2026 14:59:26 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:32 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

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

    On what planet?

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


    Either you are trolling or don't have a clue?

    Seems to be your standard response to anyone you disagree with. Go back under your bridge.

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

    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    On Mon, 2 Nov 2026 14:59:26 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:32 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

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

    On what planet?

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


    Either you are trolling or don't have a clue?

    Seems to be your standard response to anyone you disagree with. Go back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:24:07 2026
    From Newsgroup: comp.lang.fortran

    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    On Mon, 2 Nov 2026 14:59:26 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/1/2026 1:32 AM, boltar@caprica.universe wrote:
    On Sat, 31 Oct 2026 19:56:10 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Sat, 31 Oct 2026 09:47:42 -0000 (UTC)
    boltar@caprica.universe wrote:

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

    On what planet?

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


    Either you are trolling or don't have a clue?

    Seems to be your standard response to anyone you disagree with. Go back under
    your bridge.


    Before you listen to this, be sure to not in a mood to get really pissed
    off:

    https://youtu.be/mrKKBBUQnYg

    ;^) too late. Your fate of windows is misguided. It has some fun things.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 11:24:54 2026
    From Newsgroup: comp.lang.fortran

    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

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

    Michael S <already5chosen@yahoo.com> gabbled:

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

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

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

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


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

    No I don't mean that and I can't be bother explaining what multiplexing means to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Like, search for "unix select", or something?

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:34:52 2026
    From Newsgroup: comp.lang.fortran

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

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

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

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

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

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

    Unisys released the OS as part of their massively parallel
    OPUS computer system.

    There are many ways to handle proper sync in multiprocess systems. Indeed.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:36:44 2026
    From Newsgroup: comp.lang.fortran

    On 10/26/2026 10:56 PM, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 19:51:23 -0700, Chris M. Thomasson wrote:

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

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

    Keeping them up to date is, afaict, manual.

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

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

    Example from my system:

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

    Where did these come from?

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

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

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

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

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

    Windows isnrCOt even in the same league, is it.

    Windows is there. :^D
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From 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: comp.lang.fortran

    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
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 02:48:17 2026
    From Newsgroup: comp.lang.fortran

    On 10/27/2026 11:36 AM, Scott Lurndal wrote:
    Peter Flass <Peter@Iron-Spring.com> writes:
    On 10/27/26 08:00, James Kuyper wrote:
    On 2026-10-26 17:45, Lawrence DrCOOliveiro wrote:
    On Mon, 26 Oct 2026 13:26:38 -0700, Chris M. Thomasson wrote:
    [restore snippage]>> On 2026-10-25 23:39, Lawrence DrCOOliveiro wrote: >>>>>> On Sun, 25 Oct 2026 19:11:48 -0700, Chris M. Thomasson wrote:

    A caller provided buffer is normal with a lot of API's out there. >>>>>>
    No it isnrCOt. ItrCOs not a good way to manage things, anyway: instead of
    solving the resource-allocation problem once and for all in the
    library API, you are pushing the burden onto all the client code, each >>>>>> one of which has to solve it for itself.

    ThatrCOs a dumb way to design things.

    HUH? How do you call say, fread without a user provided buffer?

    Relevance being?

    fread() uses a caller-provided buffer, which, according to your previous >>> comment, "push[es] the burden onto all the client code, each one of
    which has to solve it for itself", so according to you, "That's a dumb
    way to design things"..If that isn't your actual opinion of fread(),
    your comments need to be at least a little more nuanced to avoid
    applying to fread().

    The difference is that the size of the buffer for fread() is the maximum
    you want/expect to read. The size of an object is the size it is, not
    necessarily what you expect. If you don't provide enough space you will
    truncate.

    Which isn't a significant issue with fread, since the underlying stdio
    buffer (or kernel file cache or terminal driver buffer) will hold the
    unread information for the next call to fread.

    fread(3) is basically obsolete for most high-performance applications
    which map the file directly into the process address space (mmap).

    Ditto.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 16:22:23 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go back
    under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard Windows approach of chucking threads at everything.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 16:24:03 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote:

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

    Michael S <already5chosen@yahoo.com> gabbled:

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

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

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

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


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

    No I don't mean that and I can't be bother explaining what multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is such an
    arduous task.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 10:56:20 2026
    From Newsgroup: comp.lang.fortran

    On 11/4/2026 8:22 AM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go
    back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard Windows approach of chucking threads at everything.


    Huh? You mean a thread pool, sometimes we can oversubscribe and use
    hardware threads * 2

    I don't think you should mock IOCP. Then you would be mocking AIO, or io_uring.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 19:53:33 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 4 Nov 2026 10:56:20 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 8:22 AM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go
    back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard
    Windows approach of chucking threads at everything.


    Huh? You mean a thread pool, sometimes we can oversubscribe and use
    hardware threads * 2

    I don't care if its a thread ocean, its still threads being used where they're possibly not needed. Obviously depends on load. But if I'm writing a client such as ssh where the only I/O is via stdin and the socket I'm going to multiplex them in select() or poll(), not have 2 seperate threads.

    I don't think you should mock IOCP. Then you would be mocking AIO, or >io_uring.

    I don't give a toss about IOCP, its a windows thing.

    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Gary Scott@garylscott@sbcglobal.net to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 14:17:02 2026
    From Newsgroup: comp.lang.fortran

    On 11/4/2026 1:53 PM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 10:56:20 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 8:22 AM, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 02:22:52 -0800
    "Chris M. Thomasson" <chris.m.thomasson.1@gmail.com> gabbled:
    On 11/4/2026 12:54 AM, boltar@caprica.universe wrote:
    Seems to be your standard response to anyone you disagree with. Go
    back under
    your bridge.


    Really? Why do you have a hatred for say, IOCP? If so, you must also
    HATE AIO, or io_uring?

    I never mentioned IOCP but looking at it, yeah, looks like your standard >>> Windows approach of chucking threads at everything.


    Huh? You mean a thread pool, sometimes we can oversubscribe and use
    hardware threads * 2

    I don't care if its a thread ocean, its still threads being used where they're
    possibly not needed. Obviously depends on load. But if I'm writing a client such as ssh where the only I/O is via stdin and the socket I'm going to multiplex them in select() or poll(), not have 2 seperate threads.

    I don't think you should mock IOCP. Then you would be mocking AIO, or
    io_uring.

    I don't give a toss about IOCP, its a windows thing.
    I sometimes just reserve space in the page file and let the OS lazy write/read.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Jeroen Belleman@jeroen@nospam.please to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Wed Nov 4 23:53:55 2026
    From Newsgroup: comp.lang.fortran

    On 11/4/26 17:24, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe> wrote: >>>>
    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

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

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

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

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


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

    No I don't mean that and I can't be bother explaining what
    multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is such an arduous task.


    That's fine too, as a hint, no issue there.

    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.

    Let's leave it at that.

    Jeroen Belleman
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Michael S@already5chosen@yahoo.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 15:38:55 2026
    From Newsgroup: comp.lang.fortran

    On Wed, 4 Nov 2026 23:53:55 +0100
    Jeroen Belleman <jeroen@nospam.please> wrote:
    On 11/4/26 17:24, boltar@caprica.universe wrote:
    On Wed, 4 Nov 2026 11:24:54 +0100
    Jeroen Belleman <jeroen@nospam.please> gabbled:
    On 11/4/26 09:48, boltar@caprica.universe wrote:
    On Mon, 02 Nov 2026 16:51:47 GMT
    Charlie Gibbs <cgibbs@kltpzyxm.invalid> gabbled:
    On 2026-11-02, boltar@caprica.universe <boltar@caprica.universe>
    wrote:
    On Sun, 1 Nov 2026 21:59:41 +0200

    Michael S <already5chosen@yahoo.com> gabbled:

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

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

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

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


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

    No I don't mean that and I can't be bother explaining what
    multiplexing means

    to someone who's clearly never used it.


    Don't be so smug. You could at least give him a hint.
    If you bother enough to reply, you might as well show
    that you know.

    Right, because typing "IO multiplexing" into google or an AI is
    such an arduous task.


    That's fine too, as a hint, no issue there.

    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.

    Let's leave it at that.

    Jeroen Belleman
    Unless you didn't pay attention yet, boltar is asshole and proud at
    that.
    Or arshole? I'm not sure what is a correct spelling in his area.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From boltar@boltar@caprica.universe to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 16:39:45 2026
    From Newsgroup: comp.lang.fortran

    On Fri, 6 Nov 2026 15:38:55 +0200
    Michael S <already5chosen@yahoo.com> gabbled:
    On Wed, 4 Nov 2026 23:53:55 +0100
    Jeroen Belleman <jeroen@nospam.please> wrote:
    'Multiplexing' is a copiously overloaded concept, so a little
    bit of help to steer him into the right direction is not out
    of place.
    =20
    Let's leave it at that.
    =20
    Jeroen Belleman

    Unless you didn't pay attention yet, boltar is asshole and proud at
    that.
    Or arshole? I'm not sure what is a correct spelling in his area.

    Neither, but don't worry about it. When you've finished your little sucky
    thumb tantrum maybe mummy will pick up all the toys around your pram for you.


    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris M. Thomasson@chris.m.thomasson.1@gmail.com to comp.lang.fortran,comp.lang.c++,alt.comp.lang.rust,alt.folklore.computers on Fri Nov 6 19:22:12 2026
    From Newsgroup: comp.lang.fortran

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

    On 11/2/2026 6:42 PM, Charlie Gibbs wrote:

    On 2026-11-02, Chris M. Thomasson <chris.m.thomasson.1@gmail.com> wrote: >>>
    On 11/1/2026 11:40 AM, Charlie Gibbs wrote:

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

    connect? On Windows we use ConnectEx.

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nc-mswsock-lpfn_connectex

    For accept, AcceptEx:

    https://learn.microsoft.com/en-us/windows/win32/api/mswsock/nf-mswsock-acceptex

    Ah, but then we come to that critical clause:

    Note This function is a Microsoft-specific extension to the Windows Sockets specification.

    Yes, one more attempt to close the open socket model with
    Microsoft proprietary extensions. My code has to run under
    Linux as well. Opening the socket in a separate thread is
    guaranteed to avoid hangs, regardless of operating system.

    These are for high performance systems. But, they solve a lot of
    problems. Say your program starts to gain a lot of users?

    In our environment that should never happen.

    then using the high performance API's is not necessary for your
    "current" use case. But, well, what happens if it does happen?


    The only legitimate
    users are those that are other elements of our software package.
    Any others (or too many seemingly legitimate users) get a rejection
    message, followed by disconnection.



    --- Synchronet 3.22a-Linux NewsLink 1.2