Deleting previous text in C++

[Schmatzy]

hi i have a switch loop and i was wondering how i could delete the previous text when it loops
this is my code
[code=c]
loop: int Answer;
std::cout << "Enter a number of your choice. 11 or 12 ";
std::cin >> Answer;
switch (Answer)
{
default:
goto loop;
break;
case 11:
std::cout << "text";
break;
case 12:
std::cout << "text";
break;
}
[/code]
if the loop happens it just copies the "Enter a number of your choice. 11 or 12 "; and the previous one is still there so how do i make it delete the old one?

[pbmods]

Heya, Schmatzy. Welcome to TSDN!

I'm going to go ahead and move this thread to the C++ forum, where one of our resident Experts will be more likely to be able to help you out.

Please use CODE tags when posting source code. See the REPLY GUIDELINES on the right side of the page next time you post.

[Schmatzy]

ok i dunno anything about this forum either so thanks

[Schmatzy]

its not even close to the entire code its just that section

[ilikepython]

hi i have a switch loop and i was wondering how i could delete the previous text when it loops
this is my code
[code=c]
loop: int Answer;
std::cout << "Enter a number of your choice. 11 or 12 ";
std::cin >> Answer;
switch (Answer)
{
default:
goto loop;
break;
case 11:
std::cout << "text";
break;
case 12:
std::cout << "text";
break;
}
[/code]
if the loop happens it just copies the "Enter a number of your choice. 11 or 12 "; and the previous one is still there so how do i make it delete the old one?

Eww goto, how awful. Your code could be easily rewritten without the use of goto but that's off topic.

The only two ways I know of are:
[code=cpp]
system("cls");
clrscr();
[/code]
Both make your code un portable, though. Also, clrscr() isn't part of the C++ standard.

[Rasputin]

Eww goto, how awful.

I must share this: I was TAUGHT AT SCHOOL to use goto in VB.

At times some profs really have the skills to ruin you...

[Hunderpanzer]

I'm always wanting to learn...

What's wrong with goto ? What are it's flaws ?

[Meetee]

Use of goto is discouraged because it makes your code harder to read and maintain. This is something I have read on one site

This doesn't come up often, but sometimes, SOMETIMES a goto is necessary.
SOMETIMES a GOTO isn't necessary, but it's a better alternative.

If you have to use a goto, remember these rules:
Rule #1 with a goto: NEVER JUMP BACKWARD. Jumping backward is the hardest code to read,
you can easily replace this with a do { } while(); or other loop construct.

Rule #2 DO NOT JUMP FAR OR OUT OF THE FUNCTION! Don't jump functions or jump too far
from the goto, this starts to create messy and unreadable code.

Rule #3 Make your label jump names IN ALL CAPS and make them SELF EXPLANATORY
i.e. don't name them X or Y name them like EXIT_ON_BREAK:

Regards

[Schmatzy]

Well, I am a beginner and i just learned about looping. I'm going more into loops right now.

[Schmatzy]

But please try to stay on the topic.

[Hunderpanzer]

Use of goto is discouraged because it makes your code harder to read and maintain. This is something I have read on one site

This doesn't come up often, but sometimes, SOMETIMES a goto is necessary.
SOMETIMES a GOTO isn't necessary, but it's a better alternative.

If you have to use a goto, remember these rules:
Rule #1 with a goto: NEVER JUMP BACKWARD. Jumping backward is the hardest code to read,
you can easily replace this with a do { } while(); or other loop construct.

Rule #2 DO NOT JUMP FAR OR OUT OF THE FUNCTION! Don't jump functions or jump too far
from the goto, this starts to create messy and unreadable code.

Rule #3 Make your label jump names IN ALL CAPS and make them SELF EXPLANATORY
i.e. don't name them X or Y name them like EXIT_ON_BREAK:

Regards

Thanks zodilla, I'll keep that in mind