I started coding professionally using Visual Basic (3!). Everybody made fun of VB’s OnErrorResumeNext “solution” to error handling, which basically said if something goes wrong just move on to the next line of code. But apparently nobody knew about OnErrorResume, which basically said if something goes wrong just execute the offending line again. This would of course manifest itself as a locked app and usually a rapidly-expanding memory footprint until the computer crashed. Basically the automated version of this meme.
BTW just to defend VB a little bit, you didn’t actually have to use OnErrorResumeNext, you could do OnErrorGoto errorHandler and then put the errorHandler label at the bottom of your routine (after an ExitSub) and do actual structured error handling. Not that anybody in the VB world ever actually did this.
I started coding professionally using Visual Basic (3!). Everybody made fun of VB’s
On Error Resume Next“solution” to error handling, which basically said if something goes wrong just move on to the next line of code. But apparently nobody knew aboutOn Error Resume, which basically said if something goes wrong just execute the offending line again. This would of course manifest itself as a locked app and usually a rapidly-expanding memory footprint until the computer crashed. Basically the automated version of this meme.BTW just to defend VB a little bit, you didn’t actually have to use
On Error Resume Next, you could doOn Error Goto errorHandlerand then put theerrorHandlerlabel at the bottom of your routine (after anExit Sub) and do actual structured error handling. Not that anybody in the VB world ever actually did this.