I wanted to display "www.iloveyou.com" using the following command but it shows "ilove.comyou" . I don't understand what is the problem.
Code:int number; printf ("www."); goto x; z: printf (".com"); goto y; x: printf ("ilove"); goto z; y: printf ("you"); getch (); return 0; }
How about
printf("www.iloveyou.com");
and forgetting about silly tricks in which you have got a simple order of placement wrong
?
:P
Why are you even doing this? The goto command should be used sparingly, because it is only rarely the best way to do something.
What you've done is highlight the big problem with goto. It can lead to what is known as "spaghetti code": code that jumps from place to place in a disordered way and is hard to understand or maintain.
Code:while(!asleep) { sheep++; }
@manasij
i want to learn "goto function"........
Then you've toOriginally Posted by learning_grc
goto here ;
I simply don't have the patience to go over ALL the reasons why goto is horrible. Mostly because of terribly disorganized code? (insert Anti-Goto Order banner here)
also. It's displaying that because you're telling it to. Switch goto y; and goto z;
nvm. ^ i've been beaten
Last edited by Rodaxoleaux; 10-02-2011 at 03:31 PM. Reason: beat like a noob in CoD
Reorder the code in the order that it happens:
There you go. See how easy that was?Code:int number; printf ("www."); goto x; x: printf ("ilove"); goto z; z: printf (".com"); goto y; y: printf ("you"); getch (); return 0; }
Quzah.
Hope is the first step on the road to disappointment.
Read this to learn why goto is not a good idea for general use: Goto Considered Harmful. It does have it's place, but your code is not it.
Actually it's a pretty good example of what you want them to learn about goto:If he has a hard time sorting out that small example, then he should get the idea that it's a pain to use, and avoid it. So as far as learning experiences go, it's pretty good.
Quzah.
Hope is the first step on the road to disappointment.
"goto" is not a function.
Diagnosis: The problem is that you want to learn about "goto".
Solution: Do not learn about "goto". The less you know, 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"
Well, I would like you to learn how to program; but we can't always get what we ask for.
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.
They really should just make break and continue work with labeled loops. Then there would be no legitimate use for goto at all.
It is too clear and so it is hard to see.
A dunce once searched for fire with a lighted lantern.
Had he known what fire was,
He could have cooked his rice much sooner.
I would down mod this if I could.
You should know about goto. You should know when to use it, and how it works. Not knowing about it isn't going to help you when you run into it.
Quzah.
Hope is the first step on the road to disappointment.
The "mimic exception handler" error handling style using goto would not see goto suitably replaced by such enhanced break and continue statements.
Look up a C++ Reference and learn How To Ask Questions The Smart Way
Well, my personal belief is that, based on the conceptual design for the C language, goto's should only be used for error handling; a concept which was resolved in C++ with try and catch.
You should learn how it works, nothing really more. Are we really going to turn this into another debate about 'goto'? This has been done so many times before, and (most importantly), has never helped the OP.
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.
