Thread: goto

Code:

void Function() {
	if (!function1) goto cleanup;
	if (!function2) goto cleanup;
	if (!function3) goto cleanup;
	if (cond) {
		if (!function4) goto cleanup;

Here's an amusing modification to Hammer's original idea:

Code:

void Function( void )
{
    	fun1(1)?fun2(1)?fun3(1)?condition&&!fun4(0)?cleanup():1:cleanup():cleanup():cleanup();
}

My test code had the functions take a paremeter, which they simply returned, for easy testing. Feel free to omit the arguments to the functions, the end result will be the same.

Quzah.

What about

'continue'

Is it goto's little brother?

Originally posted by chrismiceli
Basically goto was used in several "case" statements to have
execution fall through to right after the cast statement -- kind of a
way of building in multiple "default" statements.

Um yeah. See that's what 'break' is for. To get out of a case statement.

But as they always say, it's easy to avoid goto:

Code:

while(!done)
{
    switch( state )
    {
        case 1: /*stuff*/ state = -1; break;
        case 2: /*stuff*/ state = -1; break;
        ...
        default: /*stuff*/ done=1;
    }
}

Or even simpler:

Code:

switch( state )
{
        case 1: /*stuff*/ state = -1; break;
        case 2: /*stuff*/ state = -1; break;
        ...
}
if( state < low || state > high )
{
    dodefaultstuff();
}

Where 'low' is the lowest valid state, and 'high' is the highest valid state. Pretty simple. No goto needed. See how much more cleaner the code would be without the gotos in it if you just add an if check?

Quzah.

edit: wait. I see what the deal is. pnum exists inside case 'o'. This means that no additional compares are necessary to get there which is essentially the goal.

here we go:

Code:

case 'x':
     base += 6;
case 'd':
     base += 2;
case 'o':
     base += 6;
case 'b':
     base += 2;
     //pnum:

no gotos needed. no additional compares needed. I win. Send that to your author chrismiceli