Open Menu
AllLocalCommunitiesAbout
lotide
AllLocalCommunitiesAbout
Login

Writing C++ is easy.

⁨824⁩ ⁨likes⁩

Submitted ⁨⁨1⁩ ⁨year⁩ ago⁩ by ⁨MaliciousKebab@sh.itjust.works⁩ to ⁨programmer_humor@programming.dev⁩

source

Comments

Sort:hotnewtop
  • cabbage@programming.dev ⁨1⁩ ⁨year⁩ ago

    Sounds like Rust propaganda to me >:(

    source
    • JakeHimself@programming.dev ⁨1⁩ ⁨year⁩ ago

      Tbf, you have to be pretty far with Rust to get to a point where Rust’s compiler errors stop helping you (at least, as far as I’ve seen). After that, it’s pretty much the same

      source
      • philm@programming.dev ⁨1⁩ ⁨year⁩ ago

        Yep use a little bit more deeply cascaded generic rust code with a lot of fancy trait-bounds and error messages will explode and be similar as C++ (though to be fair they are still likely way more helpful than C++ template based error messages). Really hope that the compiler/error devs will improve in this area

        source
      • Boinketh@lemm.ee ⁨1⁩ ⁨year⁩ ago

        Rust has better runtime errors, too. If you run a dev build, it should pretty much never segfault unless you use unsafe.

        source
        • -> View More Comments
  • Saneless@lemmy.world ⁨1⁩ ⁨year⁩ ago

    My favorite, since I’m not a programmer anymore, is excel

    E:Your formula has a circular reference. I ain’t doing shit till you fix it

    Me: where?

    E: In your spreadsheet, I don’t fucking know

    source
    • Eheran@lemmy.world ⁨1⁩ ⁨year⁩ ago

      Excel: taking ages to load a file Excel: There is a link to another Excel document, but I can’t access it to update the value. Me: Where? Excel: To this document. Me: … Where can I find the cell that contains this link? Excel: I don’t know noises Me: What if it is a named variable? Excel: Yes.

      source
    • sunbeam60@lemmy.one ⁨1⁩ ⁨year⁩ ago

      It’s ok, you run the expression debugger, which says the first step, which is all of the formula, will result in an error. So helpful.

      source
  • manpacket@lemmyrs.org ⁨1⁩ ⁨year⁩ ago

    Then there's Haskell that would remove (well, used to at some point) your source code file if you made any errors: https://gitlab.haskell.org/ghc/ghc/-/issues/163

    source
    • CanadaPlus@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

      The world’s angriest compiler.

      source
    • TheCee@programming.dev ⁨1⁩ ⁨year⁩ ago

      So that’s what inspired Vigil…

      source
      • KazuoZeru@lemmy.world ⁨1⁩ ⁨year⁩ ago

        Reading their page gave me a good laugh. Didn’t know about this before, and I’m glad to have learned about its existence

        source
    • xoggy@programming.dev ⁨1⁩ ⁨year⁩ ago

      When the compiler is being more helpful than you realize.

      source
    • noli@programming.dev ⁨1⁩ ⁨year⁩ ago

      That’s actually hilarious

      source
  • FreeloadingSponger@lemmy.world ⁨1⁩ ⁨year⁩ ago

    MySQL: you have an error near here.

    Me: What’s the error.

    MySQL: It’s near here.

    Me: You’re not going to tell me what the error is? Okay, near where? Here?

    MySQL: warmer.

    source
    • marcos@lemmy.world ⁨1⁩ ⁨year⁩ ago

      Oracle: You have this error in line 1

      User: Hey, no, there isn’t anything to cause this error in line 1

      Oracle: I’m telling you, it’s in line 1

      User: Hum… How many lines are in my 10 lines query?

      Oracle: 1

      source
    • christophski@feddit.uk ⁨1⁩ ⁨year⁩ ago

      MySQL: you have an error around here

      Me: that’s the entire query. If you aren’t going to tell me what the error is, can you at least narrow it down?

      MySQL: … Stfu

      source
  • ihavenopeopleskills@kbin.social ⁨1⁩ ⁨year⁩ ago

    C just shrugs and says "Seg Fault."

    source
    • rikudou@lemmings.world ⁨1⁩ ⁨year⁩ ago

      Have you tried segmenting in a non-faulty way?

      source
    • Aceticon@lemmy.world ⁨1⁩ ⁨year⁩ ago

      “Shit happenned!”

      source
    • ImpossibleRubiksCube@programming.dev ⁨1⁩ ⁨year⁩ ago

      “What!? No, YOU’RE a segmentation fault!”

      source
    • ExperimentalGuy@programming.dev ⁨1⁩ ⁨year⁩ ago

      The range those words induce is crazy

      source
  • CanadaPlus@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

    Haskell errors:

    Iä! Iä! Cthulhu fhtagn! (b -> (a -> c)) -> (b -> (c -> c)) -> a Ph’nglui mglw’nfah [[a]] Cthulhu R’lyeh wgah’nagl fhtagn!

    [45 lines of scopes]

    Once you understand the type system really well and know which 90% of the information to discard it’s not so bad, I guess.

    source
    • jibz@burggit.moe ⁨1⁩ ⁨year⁩ ago

      Why is it written in Vietnamese though?

      source
      • CanadaPlus@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

        American soldiers, when the trees have no side effects:

        source
    • marcos@lemmy.world ⁨1⁩ ⁨year⁩ ago

      GHC messages are complete and precise, usually telling you everything you need to know to understand, find, and fix the error, that may not even be on the place it’s actually detected.

      It’s also in an alien language. That’s correct.

      source
      • CanadaPlus@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

        complete and precise

        Exactly. It’s a perfectly condensed yet totally complete readout of all the data you might need for debugging. It makes mathematicians everywhere proud.

        If you don’t actually need a complete set of information about possible exotic type choices just to see you put an infix in the wrong place that’s basically not the compiler’s problem.

        (TBF, I wouldn’t want to try and mindread the programmer in my compiler either, but then I am a maths person)

        source
  • glad_cat@lemmy.sdf.org ⁨1⁩ ⁨year⁩ ago

    Rust is nice, unless you have a traits compilation error from a 3rd party library using types that are more difficult to write than C++ templates.

    source
    • philm@programming.dev ⁨1⁩ ⁨year⁩ ago

      yeah as nice as it is what you can achieve with trait-bounds there are definitely trade-offs, being compile time and error messages, and sometimes mental complexity, understanding what the trait-bounds exactly mean… I really hope, that this area gets improvement on at least the error-messages and compile time (incremental cached type-checking via something like salsa)

      source
      • Flipper@feddit.de ⁨1⁩ ⁨year⁩ ago

        I much prefer getting told of that it doesn’t match a trait than get 600 characters of which the majority is implementation detail of global allocators und from what exactly the string is derived.

        source
        • -> View More Comments
  • snor10@lemm.ee ⁨1⁩ ⁨year⁩ ago

    Yeah, but which one i cooler?

    source
    • corm@sopuli.xyz ⁨1⁩ ⁨year⁩ ago

      Rust because having a package manager is important.

      Even C has a package manager

      source
    • philm@programming.dev ⁨1⁩ ⁨year⁩ ago

      Well at least C++ definitely is far away from cool, you can imagine the rest…

      source
      • snor10@lemm.ee ⁨1⁩ ⁨year⁩ ago

        But he has a purple mohawk!

        source
    • Streetdog@lemmy.world ⁨1⁩ ⁨year⁩ ago

      Bebop, he would just submit his code to the Shredder.

      source
      • snor10@lemm.ee ⁨1⁩ ⁨year⁩ ago

        Shredder = /dev/null confirmed?

        source
  • pastermil@sh.itjust.works ⁨1⁩ ⁨year⁩ ago

    Clearly, you haven’t gcc & gdb…

    source
    • eupraxia@lemmy.blahaj.zone ⁨1⁩ ⁨year⁩ ago

      I love gcc but it can’t make nested template errors any less horrifying

      source
      • BeigeAgenda@lemmy.ca ⁨1⁩ ⁨year⁩ ago

        I would say that joke only works with template bugs, normally gcc gives fairly good directions.

        source
  • Speiser0@feddit.de ⁨1⁩ ⁨year⁩ ago

    I like how this shows how rust is designed more top down and C++ is designed bottom up.

    How compiler builders see peppa:

    Image

    deviantart.com/…/Peppa-pig-front-face-743773121

    source
    • TheCee@programming.dev ⁨1⁩ ⁨year⁩ ago

      How compiler builders see peppa:

      even number of nostrils

      Missed opportunity.

      source
  • UFODivebomb@programming.dev ⁨1⁩ ⁨year⁩ ago

    Way too short to be a real C++ error. Needs a few more pages of template gibberish.

    source
    • mormegil@programming.dev ⁨1⁩ ⁨year⁩ ago

      Syntax error: unmatched thing in thing from std::nonstd::__map<_Cyrillic, _$$$dollars>const basic_string< epic_mystery,mongoose_traits<char>, default_alloc<casual Fridays = maybe>>

      (from James Mickens’ The Night Watch, highly recommended with his other essays: mickens.seas.harvard.edu/wisdom-james-mickens)

      source
    • sunbeam60@lemmy.one ⁨1⁩ ⁨year⁩ ago

      Template<Instatiation::_1,_2,_3, Instatiation2::_1, _2<closure::wrapped<_1[map::closure_inner]>>, Outer<Inner<Wrapper<float>>>>::static_wrapper<std::map<auto>, spirit::parser::lever<int, std::array<int>>::fuck_you

      source
      • em7@programming.dev ⁨1⁩ ⁨year⁩ ago

        Sounds legit.

        source
  • TheQuantumPhysicist@programming.dev ⁨1⁩ ⁨year⁩ ago

    Ever tried using typenum numerals in Rust? 😅

    Try it and see the errors with something like typenum::U500.

    source
    • philm@programming.dev ⁨1⁩ ⁨year⁩ ago

      Or deeply cascaded generic code with a lot of trait-bounds…

      source
  • dreadedsemi@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Segmentation fault. :

    source
    • Chadus_Maximus@lemm.ee ⁨1⁩ ⁨year⁩ ago

      Core obliterated.

      source
  • ExperimentalGuy@programming.dev ⁨1⁩ ⁨year⁩ ago

    One of the reasons i started learning rust was bc of how easy it is to get into it, or at least that’s how it felt for me. It wasn’t until a few months into consistently writing that I started to encounter things that I didn’t understand.

    source
    • marcos@lemmy.world ⁨1⁩ ⁨year⁩ ago

      The good thing about Rust is that if you have no idea of any problem in your code, it very likely because your code is ok.

      On C++ things are different.

      source
  • Aceticon@lemmy.world ⁨1⁩ ⁨year⁩ ago

    “Fuck you, or not. One day, or two, or forever. Certainly when you least expect it”

    (C++ errors involving memory pointers)

    source
  • miridius@lemmy.world ⁨1⁩ ⁨year⁩ ago

    Clojure: hold my beer

    source
  • TheCee@programming.dev ⁨1⁩ ⁨year⁩ ago

    Perl is panel 1, except it’s missingno. doing the talking.

    source