|
|
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.
|
|
|
|
|
I like INTERCAL's ABSTAIN. You get statements like:
PLEASE ABSTAIN FROM CALCULATING
Also, to exit the program, you use:
PLEASE GIVE UP
The PLEASE is optional. If you don't use it enough, through, the compiler will reject your program for not being polite enough. You do have to be careful with it: using PLEASE too often will get your program rejected for excessive politeness.
|
|
|
|
|
Does it have private and public statements, too?
e.g:
PRIVATE PLEASE SHAKE_IT_BABY
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
The only people who complain about this statement are the same ones who didn't know how to use it properly.
There are only 10 types of people in the world, those who understand binary and those who don't.
|
|
|
|
|
The only way to use On Error Resume Next properly is to never use it. 
"These people looked deep within my soul and assigned me a number based on the order in which I joined."
- Homer
|
|
|
|
|
Not the best War Games paraphrase I've ever seen, but it'll do.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Just about any COBOL will fit that, ADD 1 TO COUNT for instance.
veni bibi saltavi
|
|
|
|
|
Well, PERFORM sthg VARYING FROM 1 BY 1 UNTIL COUNT > 5 could do with a little work, but your point is still 90% valid.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
Common Lisp's loop macro can be pretty interesting. It lets you do things like:
(loop for i in *random*
counting (evenp i) into evens
counting (oddp i) into odds
summing i into total
maximizing i into max
minimizing i into min
finally (return (list min max total evens odds)))
|
|
|
|
|
Bloody hell, nobody mentioned GOTO or even GOSUB. It may not be error handling bit it was/is almost as abused as RESUME NEXT.
There were some doozies in the Lotus 123 macro language as well but I can't remember them. And did you ever look under the hood of early Lotus Notes, now there was a whole collection of nightmares!
Never underestimate the power of human stupidity
RAH
|
|
|
|
|
I actually used the MUMPS language when I did a contract for the VA. No reserved word, since everything was by context:
This was actually legal MUMPS code, since all things could be shortened to the first letter:
GREPTHIS()
N S,N,T,I,K,Q S I="K",S="11",K="l1",Q="R",T="K"
I I=T D T
Q:$Q Q Q
T I I,S&K S S=S+K Q
The full blown statements weren't much better:
GREPTHIS()
NEW SET,NEW,THEN,IF,KILL,QUIT SET IF="KILL",SET="11",KILL="l1",QUIT="RETURN",THEN="KILL"
IF IF=THEN DO THEN
QUIT:$QUIT QUIT QUIT ; (quit)
THEN IF IF,SET&KILL SET SET=SET+KILL QUIT
Just to put history behind it, MUMPS was the "Massachusetts General Hospital Utility Multi-Programming System", and (colloquially) was designed by doctors.
|
|
|
|
|
I'd say the If..Then..Else statement is pretty clear, amongst many many others.
If anything, your example is a little odd, as it really doesn't tell you what it is doing - resume next what? That's not English.
(It's also an extremely dodgy technique of error handling, equivalent of enclosing every statement in:
Exception error;
try {
statement;
}
catch (Exception ex) {
error = ex;
}
Which just invites people not to bother checking the result.
May as well have a statement like
On Error Keep Calm and Carry On
"If you don't fail at least 90 percent of the time, you're not aiming high enough."
Alan Kay.
|
|
|
|
|
I still love plain old C#.
foreach(var exception in MyExceptionCollection)
try
throw exception;
catch()
continue;
|
|
|
|
|
The best bit about PERL (in fact the only good bit) is
On Error DIE
Is that why PERL programmers are becoming scarce?
We're philosophical about power outages here. A.C. come, A.C. go.
|
|
|
|
|
When I worked at CompuServe, a coworker wrote some code I was running a test harness on for connecting to the portal. His variable "IBHosed" showed up in the exception if the connection wasn't established.
|
|
|
|
|
|
See title
We can’t stop here, this is bat country - Hunter S Thompson RIP
|
|
|
|
|
It's all down to @Steve-Solomon - perhaps he didn't realize that winning the CCC yesterday means he has to post the next one which should have been today?
Either way, he is up tomorrow!
Bad command or file name. Bad, bad command! Sit! Stay! Staaaay...
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
