Thread: instead of goto

what can u use instead of goto and why is this a bad way to
write your codes

It is not liked by many because people think it creates sloppy code.

It can be prevented by making the code a function or using loops. It matters how you are using it.

somthing like this


cout<<"what's your answer";

int answer;

cin>>answer;

//if the answer is more than 10 answer again
if(answer>10)
//.........what now

I was advised that goto's are only useful for efficiently escaping deeply nested loops. But good programming shouldnt require more than about 4 levels of nesting (that'll probaby start an argument!) and I have still never used a goto statement

s how should i write the code above ^^^

Code:

cout<<"what's your answer"; 

int answer; 

cin>>answer; 

//if the answer is more than 10 answer again 
if(answer>10) 
//.........what now

change it around so it all goes inside a while loop:

Code:

int answer=99999;

while (answer>10) {
 cin >> answer;
}

if you wanted to warn after a bad answer:

Code:

int answer;
cin >> answer;

while (answer>10) {
 cout << endl << "sorry, try again" << endl;
 cin >> answer;
}

yes but i see u used cin>> one more time but that's exactly what i dont want to do


while (answer>10) {
cout << endl << "sorry, try again" << endl;
cin >> answer; /// see what i mean!
}

duno why u dont want cin>> again but try this...

int answer = 0;
cout << "Answer: ";
do
{
cin>>answer;

if(answer>10)
{
cout << "ERROR! " << endl;
}
}while(answer<10);

should work

Goto is pretty self explanatory, it makes the program goto a certain spot in the code.

Code:

int dummy;
cin>>dummy;
if (dummy==7) goto LABEL1;
cout<<"you did not enter 7";
return 0;
LABEL1:
cout<<"you entered 7";
return 0;

No one is saying that you cannot use it, but, it is just not liked by programmers. It creates very hard to read code because you have to look all over the place.