• Re: "Herb Sutter: Why C++ Is Growing and What C++26 Means for

    From Lawrence =?iso-8859-13?q?D=FFOliveiro?=@ldo@nz.invalid to comp.lang.ada,comp.lang.c++ on Sun Nov 1 05:49:53 2026
    From Newsgroup: comp.lang.c++

    On Sun, 1 Nov 2026 01:34:01 -0000 (UTC), Kevin Chadwick wrote:

    Its a PITA because you have to have it correct before it compiles,
    as opposed to C++ where you don't.

    SO much fun troubleshooting at runtime instead.

    Kidding, right?

    ItrCOs been a while since I did some C++ code, but I remember wading
    through *massive* screeds of error messages every time there was a
    type mismatch on some function argument, and the GNU C++ compiler
    would list *every single possible overload candidate*, so you got
    dozens, possibly even hundreds, of lines of messages just for one
    error. And you had to check them *all* to be sure which one you meant,
    and to figure out what to fix to get the compiler to agree.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Paul Rubin@no.email@nospam.invalid to comp.lang.ada,comp.lang.c++ on Sat Oct 31 22:57:33 2026
    From Newsgroup: comp.lang.c++

    Lawrence DrCOOliveiro <ldo@nz.invalid> writes:
    ItrCOs been a while since I did some C++ code, but I remember wading
    through *massive* screeds of error messages

    Haskell is like that too, but the trick for both Haskell and C++ is that
    the diagnostics are usually accurate about what line number has the
    error. So you can often look at the code at that location and figure
    out what is wrong, without having to examine the error message too
    carefully.

    C++ Concepts are supposed to decrease the message spew by a lot as well.
    --- Synchronet 3.22a-Linux NewsLink 1.2
  • From Chris Ahlstrom@OFeem1987@teleworm.us to comp.lang.ada,comp.lang.c++ on Mon Nov 2 11:32:40 2026
    From Newsgroup: comp.lang.c++

    Lawrence DrCOOliveiro wrote this screed in ALL-CAPS (fixed):

    On Sun, 1 Nov 2026 01:34:01 -0000 (UTC), Kevin Chadwick wrote:

    Its a PITA because you have to have it correct before it compiles,
    as opposed to C++ where you don't.

    SO much fun troubleshooting at runtime instead.

    Kidding, right?

    ItrCOs been a while since I did some C++ code, but I remember wading
    through *massive* screeds of error messages every time there was a
    type mismatch on some function argument, and the GNU C++ compiler
    would list *every single possible overload candidate*, so you got
    dozens, possibly even hundreds, of lines of messages just for one
    error. And you had to check them *all* to be sure which one you meant,
    and to figure out what to fix to get the compiler to agree.

    I see those a lot, but in almost all cases I can ignore all the
    follow-on information and go to the offending line of code and
    then *doh* slap my forehead.

    I'll admit it's a pain when you forget the closing "}" of a
    universal initializer.
    --
    "But I don't want to go on the cart..."
    "Oh, don't be such a baby!"
    "But I'm feeling much better..."
    "No you're not... in a moment you'll be stone dead!"
    -- Monty Python, "The Holy Grail"
    --- Synchronet 3.22a-Linux NewsLink 1.2