Can i use "goto" in this case, or should i use it at all?

Question

Hey guys, I need some help or rather some with sense driven opinion, its about a code-snippet i wrote for a windows forms project and specificly about the use of "goto".
I discussed it with a friend who is part of the reason i bringing the case here, because he said you should never use it. I asked my teacher about it ans even he wasnt 100% whats the best case here.
So i researched a little bit and made up my mind with a "solution" i can live with ^^.
But i want to here what your thoughts in this are because i had  alwyas great conversations here, here is the code:

for (int col = 0; col < sideLength; col++)
            {
                for (int row = 0; row < sideLength; row++)
                {
                    if (pictureBoxGrid[col,row].Bounds.Contains(centerObjectPoint))
                    {
                        pictureboxIndex[0] = col;
                        pictureboxIndex[1] = row;

                        goto SUCESS;
                    }
                }
            }
            SUCESS:

Answer 1

Marcus Otterström Why would you advise against flag variables,
i Check if a point is on one of the pictureboxes and if i Save the index of that picturebox and dont know if linq makes sense here on the Information i know or am i wrong here?

Answer 2

A lot of companies forbid goto statements so using a different method might help you in you future working career. I'd do this:
bool exit = false;
for (int col = 0; col < sideLength && !exit; col++)
{
         for (int row = 0; row < sideLength && !exit; row++)
         {
                    if (pictureBoxGrid[col,row].Bounds.Contains(centerObjectPoint))
                    {
                        pictureboxIndex[0] = col;
                        pictureboxIndex[1] = row;
                        exit = true;
                    }
         }
}

Answer 3

yes goto is usable when trying to break out of nested loops, but other than that, i don't advise it

Answer 4

John Wells thats exactly how i changed just the variable is still called sucess ^^ i think personally thats the best solution, because everyone can understand it and it is not "complex".

nice to know that companies do that.

I wouldnt use goto again because it is confuses more than it solves
and it is not really known anymore

Answer 5

hinanawi thats what i thought first to, it is really useful but not necessary and the "negatives" just outrun the use of it

Answer 6

Marcus Otterström how would you change the Code?

Answer 7

would only go out of the first for thats Why i used it

Answer 8

Marcus Otterström its just little difference and a personal opinion of mine but i like the Version of John Wells more but thanks for your ways, to seperated it in to a method is a really nice idea and i would do that probally in the future too, whats your opinion on this way?