TunaCowboy
link
fedilink
621Y

Have you considered learning how to read a stacktrace?

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?!

so said EVELYN the modified DOG

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

Well, everyone knows what that means.

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.

Tell me the values of the variables involved,

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

ZeroCool
link
fedilink
English
471Y

Jokes on you, I don’t even know how to read.

Damn, got us good!

Create a post

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

  • Posts must be relevant to programming, programmers, or computer science.
  • No NSFW content.
  • Jokes must be in good taste. No hate speech, bigotry, etc.
  • 1 user online
  • 38 users / day
  • 138 users / week
  • 529 users / month
  • 2.24K users / 6 months
  • 1 subscriber
  • 1.68K Posts
  • 37.1K Comments
  • Modlog