• erogenouswarzone@lemmy.ml
      link
      fedilink
      English
      arrow-up
      17
      arrow-down
      6
      ·
      1 year ago

      It is 2023 my brother in christ! We deserve better error outputs than a stack trace.

      1. Tell me what line in my file caused the error,
      2. Tell me the values of the variables involved,
      3. Then you can have the stack trace.

      Why are we pretending like these error messages are acceptable in 2023?!

      • segfault@lemmy.world
        link
        fedilink
        arrow-up
        5
        ·
        1 year ago
        so said EVELYN the modified DOG
        

        (This is not just a Zappa quote, but an actual error description from the Small Device C Compiler.)

      • pingveno@lemmy.ml
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        Tell me the values of the variables involved,

        There be dragons! Sounds like a good way to get passwords/secrets logged.

      • Yawnder@lemmy.zip
        link
        fedilink
        arrow-up
        3
        ·
        1 year ago

        I can’t tell if that was sarcasm or not. If it was, you got me. If it wasn’t, then that’s quite a big lack of understanding of what’s actually happening.