Mirage Source

IS there anyway to make a on error resume next on just 1 line of code?

_________________

I don't think so, make a new function and add only this one line of code...

_________________
http://www.blackages.com.br

From my understanding "on error resume next" is bad mojo and would probably be best to find another way around it. What exactly is the problem?

_________________
NetGore Free Open Source MMORPG Maker

Thats what I said basicly, I dont want a on error resume next code. I want it to work just for 1 line of code.


Are you sure the On Error Resume Next wont act below On Error Goto 0 too?

The bug is when you open for example counterstrike and have a ms game running. I just want a way around it. I will just add that line of code into a new sub and add a on error resume next there.

_________________

On Error Resume Next pretty much says to just push all errors into the Err object, but keep executing the statements (don't break execution) no matter what.

On Error Goto 0 turns this state off and returns the error-handling to it's regular (if something happens, shut everything down and complain a lot) state.

Also, error handling is local for every subroutine. If you put On Error Resume Next at the top of the sub, there is an implied On Error Goto 0 as soon as program execution leaves that subroutine (whether by returning a value, or by hitting an Exit Function, Exit Sub, End Function, or End Sub).

The code that Spodi posted will make sure that the single line of code you put between the statements will be run no matter what, and if there is an error, it'll simply be logged in the Err object and then ignored.

VB has pretty weak error handling, in my opinion. All you can really do is On Error Resume Next or On Error Goto Label, and just use If Err.Number > 0 Then to check if there even was an error.

_________________

William sir, I don't think people are gonna freak out about that bug. No ones gonna tab over between a mirage game and counter strike between rounds.

_________________

'On Error Resume Next' has it's places

For example, if something you do has the potential of failing, and if it failed you want to do something and try again.

Say, I want to save the file... but the folder doesn't exist.

_________________

Why not try my app, ColorEye, on your Android devlce?
Do you like social gaming? Fight it out in Battle Juice!

I am a professional software developer in Salt Lake City, UT.

I do.

_________________

On Error Resume Next actually isn't too bad. Its kinda like a simplified, unstructured version of Try/Catch blocks.

_________________
NetGore Free Open Source MMORPG Maker

Doesn't error handling have to be turned on for every individual subroutine, though?

With C++, if you have a function inside of a try block that throws an exception, then the exception isn't just local to the function - it goes all the way back to the try block and then to the catch block (if there is one).

With On Error Resume Next, don't you have to explicitly set it for every subroutine?

Even if you had:


If I'm correctly remembering what I read in an article about error handling in VB, you'd have to put On Error Resume Next inside of the definition for SomeSubThatWillError(), otherwise, when you raise the error, it will cause the program execution to terminate even though the sub is within an On Error Resume Next/On Error Goto 0 block.

Then again, I could be completely wrong... =x

_________________

I think On Local Error Resume Next is just for the routine itself. On Error Resume Next works for the subroutines, too. Not positive, though.

_________________
NetGore Free Open Source MMORPG Maker