|
Most TrySomething (like TryParse) methods swallow exceptions if you don't check for the return value.
The if-statement can be just as harmful. Take those huge nested if-else branches. Impossible to test, impossible to change (without breaking everything).
So we replace the if-statements with switch/case-statements, same thing happens.
We need to loop through some collection, but it's kind of recursive, and now some programmer uses foreach foreach foreach... (yeah, I've seen it happen).
In SQL Server when an exception occurs it's more or less swallowed UNLESS you use try-catch (how many programmers know that?).
So I now shouldn't use catch, TryParse, if, switch/case, foreach, and SQL Server 
Well, I agree ON ERROR RESUME NEXT is the most useless of them all
|
|
|
|
|
You're absolutely right about the huge nested ifs, I usually tend to modularize a lot and where multiple checks are involved I use a SEQUENCE of if and a cumulative status, so that it becomes
bool keep_going = true;
if (error_cond1) keep_going = false;
if (keep_going && error_cond2) keep_going = false;
...
It's easier to read and modify, also it's not mandatory to have a single cumulative status. Since I work with stdcalls, VB6 and plain old C code on old compilers (long story short: we can't change.) I can't reliably use exceptions outside the deepest functions and being the VS6 stdlib what it is I don't really need them since it's better to stick to CRT functions, which don't have exceptions. Being VS6 CRT what it is many "safe" functions that use SEH exceptions do not exist so I don't use them either.
GCS d--- s-/++ a- C++++ U+++ P- L- E-- W++ N++ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t++ 5? X R++ tv-- b+ DI+++ D++ G e++>+++ h--- ++>+++ y+++* Weapons extension: ma- k++ F+2 X
If you think 'goto' is evil, try writing an Assembly program without JMP. -- TNCaver
When I was six, there were no ones and zeroes - only zeroes. And not all of them worked. -- Ravi Bhavnani
|
|
|
|
|
I think you could also put in a "goto" instead of setting "keep_going" if you want to break up that nested if architecture.    
|
|
|
|
|
If your code is something like this
try {
statement
} catch () {}
try {
statement
} catch () {}
...
Then the ON ERROR RESUME NEXT statement makes sense. I actually use it on occasion where I have a short procedure and I want the errors to be consumed and don't care what they are. Doesn't happen often but it does every now and then.
|
|
|
|
|
I think you need
catch (void) {} At least in C++ you can throw any type, not just derivations of
class Exception
|
|
|
|
|
|
MOVE CORRESPONDING
Still waiting for one of the "modern languages" to implement that one.
(I have to resort to reflection in C#).
|
|
|
|
|
Best line ever.
I think every language should have something like 'On Error Resume Next'. Once I added it, my program stopped crashing entirely! It's like magic! Imagine if we could just apply this to every application worldwide... No more software bugs!
(Before you start screaming, note the joke icon... Seriously... I'm crazy, but I'm not an idiot)
|
|
|
|
|
You'd have to go a long way to beat the eloquence of this:
$HODOR: hhodor? Hodor!? Hodor!? oHooodorrhodor orHodor!? d = HoDoRHoDoR () {
hodor.hod('Hhodor? Hodor!? Hodor!? o HODOR!? orHodor!? d!');
};
hhodor? Hodor!? Hodor!? oHooodorrhodor orHodor!? d();
Hodor Programming Language[^] 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
I would go a long way.............to beat the persons who come up with that!
"the debugger doesn't tell me anything because this code compiles just fine" - random QA comment
"Facebook is where you tell lies to your friends. Twitter is where you tell the truth to strangers." - chriselst
"I don't drink any more... then again, I don't drink any less." - Mike Mullikins uncle
|
|
|
|
|
Richard Deeming wrote: Hodor Programming Language[^]
That would be funnier if it didn't look almost exactly like a lot of the Java code I've had to manage.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The modern version;
catch
{
}
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
Not quite - the modern version would require wrapping every single statement in its own "Pokémon exception-handling" block.
Which would mean splitting all variable declarations from their assignments, since a variable declared inside a try block can't be used outside of that block.
Which would also mean giving every variable some sort of default value, either when they're declared, or in the empty catch block for the first line that assigns them.
And don't forget to update the properties of the global Err object, in case the user gave any thought to checking for errors on the following line, and didn't just let their code trundle on regardless and destroy the program state / database / computer / world.
Having worked with VBScript many years ago, where this was the only form of error handling allowed, it's an horrendous construct. Whoever came up with the idea deserves a good beating with the clue-bat.
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Richard Deeming wrote: Whoever came up with the idea deserves a good beating with the clue-bat.
Probably someone who got paid per LOC.
Bastard Programmer from Hell
If you can't read my code, try converting it here[^]
|
|
|
|
|
You hold 'im, I'll hit 'im.
Then we can swap places. Repeatedly.
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
|
Richard Deeming wrote: he modern version would require wrapping every single statement in its own "Pokémon exception-handling" block.
Which would mean splitting all variable declarations from their assignments, since a variable declared inside a try block can't be used outside of that block.
Which would also mean giving every variable some sort of default value, either when they're declared, or in the empty catch block for the first line that assigns them.
And don't forget to update the properties of the global Err object, in case the user gave any thought to checking for errors on the following line, and didn't just let their code trundle on regardless and destroy the program state / database / computer / world
Ah!
Now I understand why you love VB so much!
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
That's more like ON ERROR BAIL.
Steve
|
|
|
|
|
|
You've discovered infinite recursion 
Remain Calm & Continue To Google
|
|
|
|
|
"IF THEN MAYBE", "DO SOMETHING" and "GO SOMEWHERE" have always had a special place in my heart....
MAYBEBOL
|
|
|
|
|
I like their error-handlers, at least it is honest.
Bastard Programmer from Hell 
If you can't read my code, try converting it here[^]
|
|
|
|
|
ON ERROR FORGET ABOUT IT from MAYBEBOL seems to be most directly in the spirit of the OP.
Software Zen: delete this;
|
|
|
|
|
I've worked at places where it's ON ERROR RESUME UPDATE.
(You'll have to imagine the accents)
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
DaveAuld wrote: just popped into my head
I mumble this when something goes wrong...of course the wife doesn't get it. 
It's the be-all, catch-all of error handling constructs, and not a bad way to approach life sometimes! I can always apply a condition based on Err.Number!
"Go forth into the source" - Neal Morse
|
|
|
|
|
break;
The language is JavaScript. that of Mordor, which I will not utter here
This is Javascript. If you put big wheels and a racing stripe on a golf cart, it's still a f***ing golf cart.
"I don't know, extraterrestrial?"
"You mean like from space?"
"No, from Canada."
If software development were a circus, we would all be the clowns.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
