Imagine 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.
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 ONERRORRESUMENEXT will ignore.
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.
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 NEXTwill ignore.