Incase it doesn’t show up:

  • Treczoks@lemmy.world
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    16 days ago

    I’ve seen way worse. Imagine a project that uses C preprocessor structures to make a C-compiler provide a kind-of C++. Macros that are pages long, and if you forget a single bracket anywhere, your ten pages look like a romance novel.

    Or VHDL synthesis messages. You’ve got no real control over them, 99.9% of the warnings are completely irrelevant, but one line in a 50k lines output could hint at a problem - if you only found it.

    So far, the output of C or C++ compilers (except for the above-mentioned project) has not been a problem or me, but I’m doing this for about 40 years now, so I’ve got a bit of experience.

    • xthexder@l.sw0.com
      link
      fedilink
      arrow-up
      6
      ·
      16 days ago

      Yep, sadly I’ve been exposed to a few such codebases before. I certainly learned a lot about how NOT to design a project.

      You’ve been at it longer than I have, but I’ve already had coworkers look at me like I’m a wizard for decoding their error message. You do get a feel for where the important parts of the error actually are over time. So much scrolling though…

      • Treczoks@lemmy.world
        link
        fedilink
        arrow-up
        2
        ·
        16 days ago

        Yes, I have my share of coworkers asking me when they run into problems, too. They even ask me when they have Windows problems. And I don’t do Windows - I do Linux and embedded systems.