This question is actually a result of an [interesting discussion](http://www.reddit.com/r/programming/comments/8cx8m/error_handling_in_c_you_are_going_to_fail_in_a/) at programming.reddit.com a while ago. It basically boils down to the following code:

```
int foo(int bar)
{
    int return_value = 0;
    if (!do_something( bar )) {
        goto error_1;
    }
    if (!init_stuff( bar )) {
        goto error_2;
    }
    if (!prepare_stuff( bar )) {
        goto error_3;
    }
    return_value = do_the_thing( bar );
error_3:
    cleanup_3();
error_2:
    cleanup_2();
error_1:
    cleanup_1();
    return return_value;
}

```

The usage of `goto` here appears to be the best way to go, resulting in the cleanest and most efficient code of all possibilities, or at least so it seems to me. Quoting Steve McConnell in *Code Complete*:

> 
> The goto is useful in a routine that
>  allocates resources, performs
>  operations on those resources, and
>  then deallocates the resources. With a
>  goto, you can clean up in one section
>  of the code. The goto reduces the
>  likelihood of your forgetting to
>  deallocate the resources in each place
>  you detect an error.
> 
> 
> 

Another support for this approach comes from the *Linux Device Drivers* book, in [this section](http://www.xml.com/ldd/chapter/book/ch02.html#buierr).

What do you think? Is this case a valid use for `goto` in C? Would you prefer other methods, which produce more convoluted and/or less efficient code, but avoid `goto`?