It's already a debate about goto.Originally Posted by AndrewHunter
Quzah.
It's already a debate about goto.
Quzah.
Hope is the first step on the road to disappointment.
I understand that this is an ongoing debate; my question is mainly should we always start this debate everytime a newb asks about goto? It really seems counter-productive. "We" understand this debate however, in most cases, the newb will not and thus could derive false conclusions.This is, one of the many, reasons I have considered the possibility of starting a "members only" kind of programming site.
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
It's a knee jerk reaction. Instead of just answering his question, everyone has to point out why he should never ever use goto and shouldn't even learn about it. I'm not saying it's right or wrong, it's just what everyone does.
Quzah.
Hope is the first step on the road to disappointment.
I would tend to agree with your concept, however I believe base on the OP's code and questions, the conservative route in this case was appropriate.
Now, are there reasons to use goto in C? My answer would be yes. Even more so, sometimes the reason to use it may seem convoluted and not immediately apparent (John Carmack), however this was not the case. Personally, I would prefer the concept buried in the language until at least 3rd or 4th year level; past once you understand what exactly the effect of your code is on the computer.
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
I wish I could make labels be nubmers.That way I could pretend I was programming in BASIC.Code:10: printf( "hello world\n" ); 20: goto 10;
Quzah.
Hope is the first step on the road to disappointment.
Haha...we all wish we could go back to those days......
Unfortunately..................................... ................
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
Unfortunately, someone knocked the top of your dino's head off.
Quzah.
Hope is the first step on the road to disappointment.
LOL.....who wanted that code highlighting anyway.
EDIT: Ok that was suppose to be the "roll eyes" smiley but I received the "window licker on the special bus smiley". I would like to lodge a complaint......
Warning: Some or all of my posted code may be non-standard and as such should not be used and in no case looked at.
You could approximate that, e.g.,
then claim that this is M BASICCode:M10: printf( "hello world\n" ); M20: goto M10;
Look up a C++ Reference and learn How To Ask Questions The Smart Way
the order is as follows:
Code:int number; printf ("www."); goto x; z: printf ("you"); goto y; x: printf ("ilove"); goto z; y: printf (".com"); getch (); return 0; }
vikasvijayan, don't you ever read the previous responses to the threads that you reply to?
Look up a C++ Reference and learn How To Ask Questions The Smart Way
All he did is take the code box from the first post and hit enter after every line.
Quzah.
Hope is the first step on the road to disappointment.
Sounds like an FAQ in the making...
Let me rephrase: The less you know about goto in the early stages of learning a programming language, the better.
My homepage
Advice: Take only as directed - If symptoms persist, please see your debugger
Linus Torvalds: "But it clearly is the only right way. The fact that everybody else does it some other way only means that they are wrong"
The guys who wrote "Numerical recipes" make an interesting point regarding goto. They say it's not the goto itself that is the problem, but the label it branches to. When you see a label you immediately think "Uh oh! Now I have to find what bit of code transfers control here". I'm not sure I agree, particularly if the label is well-named and you never use goto to jump backwards, but I get their point.
Code:while(!asleep) { sheep++; }
