Do not use goto it is a clear sign of what is called spaghetti code. Dreza has provided a much better solution. You routines should be tightly cohesive meaning they do one thing and they do it well. Only wrap calls in try/catch if the call might throw an exception then handle the exception and continue execution.

I hope this helps.

Do not use goto as it is a clear sign of what is called spaghetti code. @dreza has provided a much better solution. You routines should be tightly cohesive, meaning they do one thing and they do it well. Only wrap calls in try/catch if the call might throw an exception, then handle the exception and continue execution.

Do not use goto it is a clear sign of what is called spaghetti code. Dreza has provided a much better solution. You routines should be tightly cohesive meaning they do one thing and they do it well. Only wrap calls in try/catch if the call might throw an exception then handle the exception and continue execution. Check out my blog for some tutorials http://www.refactorthis.net

I hope this helps.

Do not use goto it is a clear sign of what is called spaghetti code. Dreza has provided a much better solution. You routines should be tightly cohesive meaning they do one thing and they do it well. Only wrap calls in try/catch if the call might throw an exception then handle the exception and continue execution.

I hope this helps.