if else
how can you use an if statement to go back to the beginning of your code.
Im trying to give the user the option to restart the program without exiting the program.
For example, the output on the screen will be:
Would you like to continue using this program? [y/n]
so the how should the code read????
Please help, this is wrecking my headCode:if (c == 'y'|| c == 'Y') { ????? ?? ????? } else printf("\n\nThe program is now finished. Thank you!");
Last edited by Salem; 11-01-2007 at 03:04 PM. Reason: Fix position of code tags
Normally you'd use a loop:
Something like that. ...and the [code][/code] tags don't go around everything in your post, just the code.Code:do { Do stuff Ask user if they'd like to go again }while( c == 'y' || c == 'Y' ); printf("\n\nThe program is now finished. Thank you!");
"Owners of dogs will have noticed that, if you provide them with food and water and shelter and affection, they will think you are god. Whereas owners of cats are compelled to realize that, if you provide them with food and water and shelter and affection, they draw the conclusion that they are gods."
-Christopher Hitchens
I think that you can do this
but it is a bad programming practice....Code:if(c=='y'||c=='Y') { main(); }
Last edited by sreeramu; 11-01-2007 at 08:12 PM.
Did you mean main()? Recursive calls to main are strongly discouraged, see here.Originally Posted by sreeramu
"Owners of dogs will have noticed that, if you provide them with food and water and shelter and affection, they will think you are god. Whereas owners of cats are compelled to realize that, if you provide them with food and water and shelter and affection, they draw the conclusion that they are gods."
-Christopher Hitchens
You can also use a goto statement, although goto is generally considered a sloppy hack in most cases and is almost never preferable over other techniques like loops...
I know that but i am telling him that this way is also possible...
You can use
Code:for(;;) { ......... } and while(1) { ......... }
I think that goto is also a bad programming practice....
In most cases, you're right. Although there are a few situations (such as deeply nested loops) where it can actually make the code clearer.
friend......first during initial stage of the program, store status of environment in a buffer and when it is needed go back to that position.....following code explains it..
Code:#include <stdio.h> #include <setjmp.h> jmp_buf task; void child(); int main() { int i; i=setjmp(task); if(i==0) { printf("hello"); child(); } else printf("world"); return 0; } void child() { longjmp(task,1); }
I know goto is a bad programming practice, but will it hurt just to use it to go back to the beginning of the program?
after declaring your variables, put an identifier (e.g. beginning).then make an if like the one you posted in the beginning, with a goto statement.Code:beginning:Code:if (c == 'y'|| c == 'Y') goto: beginning; else printf("\n\nThe program is now finished. Thank you!");
The proper solution was given by hk_mp5kpdw in post 2.
Whatever you do, don't call main like that to restart the program. It's a bad practice, and it will lead to a stack overflow error if the game is restarted enough. The fact that the function is main has nothing to do with it; A recursive function should always have a guaranteed end to the recursion.
Goto will work, but when deciding between using goto and a loop, a loop is always better. It's easier to read, and easier to change.
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'm not disagreeing with you. But I'm curious. Why not use a goto statement in an obvious case like this? I use loops in the middle of programs. But it can be more complicated there.
What's the problem with a goto in an obvious case like this? isn't it more efficient? and it is more readable (at least I feel it is)
no they're both just 'jmp's.
For a simple case like this, goto is not warranted. Post #2 is the best way for your program.
Efficiency is irrelevant in this program unless you're using a computer from the 70's. Also, since computers today use branch prediction algorithms, a loop is easier for them to predict and optimize than a goto which can jump anywhere in the code.
