Is using goto a bad practice

[VladimirF]

here is a very readable way to breakout of nested loops.

for(size_t i = 1, break_loops = 0; i < 10 && !break_loops; i++)
{
	for(size_t j = 0; j < 10 && !break_loops; j++)
	{
		if(WHAT_EVER)
			break_loops = 1;
	}
}

If you'd have a little more code in your loop (like in some real life example):

for(size_t i = 1, break_loops = 0; i < 10 && !break_loops; i++)
{
	for(size_t j = 0; j < 10 && !break_loops; j++)
	{
		if(WHAT_EVER)
			break_loops = 1;
	}
	// MORE CODE HERE
}

the part "// MORE CODE HERE" will still be executed, unless, of course, you add multiple tests for "break_loops", wich doesn't help the things. Think about more than two nested loops. If the code is trivial - almost any solution will be readable.
About SuperKoko's suggestion of multiple return statements - I believe it isn't much better than goto's, and sometimes - much worse.
P.S. When we are done with goto, lets talk about use of tabs vs. spaces for indentation.