Question

Generally speaking goto is bad (we all know why) What would be a better way to implement a simple cleanup on an error (as in the example below) without having to duplicate the code. To my mind the code below is fine, I was just curious what others would do:

int main (int argc, const char * argv[]) {
    NSAutoreleasePool * pool = [[NSAutoreleasePool alloc] init]
    int returnCode = 0;

    // ... Other code

    // WRITE: To file
    if([dataStore writeToFile:savePathData atomically:YES] == NO) {
        NSLog(@"writeToFile ... Error");
        returnCode = 1;
        goto cleanUpCode;
    }

    // ... Other code

    // Clean up
    cleanUpCode:
    [archiver release];
    [newPlanet release];
    [pool drain];
    return(returnCode);
}

EDIT_001:

In general terms I agree that @try, @catch, @finally are more than certainly the way to go but I do have two small concerns.

(1) The three @try, @catch, @finally blocks must all be together, you don’t have the flexibility to place code between the @catch and @finally that you might want to bypass.

(2) Apple’s documentation for Obj-C 2.0 states the following: “Important: Exceptions are resource-intensive in Objective-C. You should not use exceptions for general flow-control, or simply to signify errors (such as a file not being accessible)”.

much appcreciated

gary

Answer 1

This is a common idiom in C code, and I don’t think there is anything wrong with it in the absence of a language with more comprehensive creation/destruction semantics.

Goto is considered harmful in the general sense; it can make program execution difficult to follow. Here, it’s very limited in scope, and the flow is unidirectional. It’s also helpful in the sense that it allows you to localize your cleanup code, which is a good thing.