- cross-posted to:
- [email protected]
- cross-posted to:
- [email protected]
You must log in or register to comment.
Ship it.
Like putting electrical tape over your check engine light.
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
Average node bug solving
process.on('uncaughtException', console.error)
That’s fucking hilarious
except: passI 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 their machine though!
Donald Trump does coding.
Push it to prod & see the world burns around you
@Irelephant “Fixed dem warnings boss.”
Still not as excellent as
On Error Resume NextImagine the sheer
idiocygenius 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 -ePowerShell 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.
So catching errors and doing nothing? That exists in every language except maybe BASIC?
Catching individual errors is fine. Having all errors be ignored by default is weird.
deleted by creator
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.
