I keep getting Clang errors on the following type of code and I can&#39;t figure out why they&#39;re erroneous or how to resolve them to Clang&#39;s satisfaction:

    + (NSString *)checkForLength: (NSString *)theString error: (NSError **)error {
    	BOOL hasLength = ([theString length] &gt; 0);
    	if (hasLength) return theString;
    	else {
            *error = [NSError errorWithDomain:@&quot;ErrorDomain&quot; code:hasLength userInfo:nil];
            return nil;
    	}
    }

Leaving aside the utterly-contrived nature of the example (which Clang did object to so it&#39;s illustrative enough), Clang balks at the error assignment line with the following objection:

&gt; Potential null dereference. According to coding standards in &#39;Creating and Returning `NSError` Objects&#39; the parameter &#39;error&#39; may be null.

I like having a pristine Clang report. I&#39;ve read the cited document and I can&#39;t see a way to do what&#39;s expected; I checked some open-source Cocoa libraries and this seems to be a common idiom. Any ideas?

All Clang Static-Analyzer Solutions on Gang of Coders

Total of 1 Clang Static-Analyzer Solutions

Clang Error on "Potential null dereference."