Printable View
Well, I'm reading a C++ Book. It says that using the goto command in C++ is shunned by programmers. I'm just wondering if that applies to vb...
Now not being an expert programmer, I've found the goto command very useful in vb to get out of loops, and just to streamline my whole code.
So thats the question at hand... Is goto an acceptable command in VB?
-Edited by Cimperiali to add two more options
Good question for debate....I think what your c++ source is intimating is the notion of 'spaghetti code' which is an archaic style of programming. In today's world of modular and object oriented approaches, using goto statements to jump around various bits of logic is indeed frowned upon, however, in VB, the goto is obviously needed in the error handling department (on err goto error_trap ie.) This sort of flow control is certainly useful, but if you are using goto to jump to various parts of code that could be encapsulated in a sub or function (perhaps within a class or module) the latter is definately preferred. Otherwise, altering the app down the road would be nightmarish, not to mention the great advantage in terms of code reusibility that is gained with the modular approach....and that's my two cents...next!!
DA
I think you need to modify the poll to add "It Depends"
I don't think any of the poll answers actually reflect what I think. It is good (and pretty much imperative for error handling), but I've seen it used in some pretty crazy ways!
Used properly and not to excess its excellent. I like it...
but like TwoDogs said, it can be misused.
Yes GOTO has its own place in coding. In some cases like error handling we have no other option but GOTO.
But i think i is not good idea to use this command in any logic. GOTO is makes code less-readable and less-undertandable.
Well there's no harm in GOTO as long as it is handled properly. In fact, it is useful in many ways!
It's the fastest 'jump' because it doesn't have the overhead of inserting return address to the stack that are common on jump commands for those so-called 'structured' programming languages.
And usually avoid it as long as I can in normal code.
But I accept it as long as you're able not to make code obfuscated
That is: Clarity of code (not only for me but also for those who may follow) is a priority to which I am ready to sacrify time (mine, in coding more, and of Pgm in quikness).
Have a nice day, you all
Cesare Imperiali
It depends of the use of the GoTo, most of the time, it can be avoided, however, I think it can make a good Exit Function substitute.
Lets think about a validation function validating many entries. You will probably have to use Exit Function now and then, like:
If not IsNumeric(Variable) Then
Exit Function
End if
However, you could want to replace the Exit Function by a GoTo EndOfFunction, so you can do additionnal thing when the function exit, like resetting the MousePointer of the screen to normal.
Most of the times, you can avoid (or replace) a GoTo by using imbricated IF, Select statement and Loop. Also, naming the Goto Label is important. I did never use Goto except for error trapping and to replace Exit function, it can be avoided in most of the case ;)
JeffB