goto help?

I need help with the goto function. whenever i set a label and click goto, it goes to that one...and only that one. if i put another label and set a goto and the name of that label as goto, it goes to the first ( here is an example).
Staraws: cout << "Hello" << endl;
goto Starasw;

JWRW: cout << "testing" << endl;
goto JWRW ( it goes to the first one though)

Here is the source code for my project if that will help.

I can't think of an explanation for this behavior, but I would suggest a round about solution that solves another design flaw: don't use goto.

Goto is often looked down upon in C/C++ circles, as these higher-level language have developed much better control structures than goto. Although goto does sometimes have a purpose - it's almost never the best option. I would strongly recommend you redesign your program flow to use functions and loops, etc...

oops, this was a problem on my part ( and a really stupid mistake).
Next time i'll try harder to solve a problem before whining about it.

I think I've used goto one time. It was to bypass some text getting sent to stdout.

Code:

---

if(suchcode == something){Goto NullOut;}
    printf("%d\n", suchcode);

NullOut:
    ;;

---

Then again whatever it was only got used for debug purposes, and really didn't need to be there anyway. You're better off with calling a function than getting confused later on (if you program grows in size) with all of the labels that you have created, etc.

Quote:

---

Originally Posted by Wolve

I think I've used goto one time. It was to bypass some text getting sent to stdout.

Code:

---

if(suchcode == something){Goto NullOut;}
    printf("%d\n", suchcode);

NullOut:
    ;;

---

---

Why not

Code:

---

if(suchcode != something)
  printf("%d\n", suchcode);

---

Same affect.

Goto is one of those things that if you have to ask if you should use it then you shouldn't use it.

My point exactly lol