@Irelephant "Fixed dem warnings boss."
Programmer Humor
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.
except: pass
Push it to prod & see the world burns around you
That's fucking hilarious
Like putting electrical tape over your check engine light.
I came across a stack overflow recently about how to do something in a jasmine unit test. Someone gave a solution of “I just changed the test to xit(“…
and now there are no errors!”
It works on his machine though!
I wrap every line of code in a try catch block, even my try catch blocks are in try catch blocks just in case the first accidentally drops it after catching it
Yo dawg, I heard you like try-catch blocks
Donald Trump does coding.
Ship it.
Still not as excellent as On Error Resume Next
Imagine the sheer ~~idiocy~~ genius required to add a language feature where, if an error occurred, the handling method is to just pretend that line of code never existed and continue onto the next line.
VBA is truly the language of savants.
set -e
So catching errors and doing nothing? That exists in every language except maybe BASIC?
Very different. This means default ignore all errors and continue to the next line. You’d have to explicitly catch every line in most(all?) other languages.
Ignoring every exception, including divisions by zero, is something I've never seen outside of BASIC and shell scripting. Even C and assembly will shit themselves when you do some of the shit that ON ERROR RESUME NEXT
will ignore.
Catching individual errors is fine. Having all errors be ignored by default is weird.
PowerShell does that by default, and it's my least favorite feature in my most used language.
$ErrorActionPreference = Stop
At the start of almost every script.
set -e
Average node bug solving
process.on('uncaughtException', console.error)