Sign Up

Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.

Have an account? Sign In

Have an account? Sign In Now

Sign In

Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.

Sign Up Here

Forgot Password?

Don't have account, Sign Up Here

Forgot Password

Lost your password? Please enter your email address. You will receive a link and will create a new password via email.

Have an account? Sign In Now

You must login to ask a question.

Forgot Password?

Need An Account, Sign Up Here

Please briefly explain why you feel this question should be reported.

Please briefly explain why you feel this answer should be reported.

Please briefly explain why you feel this user should be reported.

Sign InSign Up

The Archive Base

The Archive Base Logo The Archive Base Logo

The Archive Base Navigation

  • SEARCH
  • Home
  • About Us
  • Blog
  • Contact Us
Search
Ask A Question

Mobile menu

Close
Ask a Question
  • Home
  • Add group
  • Groups page
  • Feed
  • User Profile
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Buy Points
  • Users
  • Help
  • Buy Theme
  • SEARCH
Home/ Questions/Q 3699284
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 19, 20262026-05-19T05:05:03+00:00 2026-05-19T05:05:03+00:00

I got into the habit of coding my error handling this way: NSError* error

  • 0

I got into the habit of coding my error handling this way:

 NSError* error = nil;
 NSDictionary *attribs = [[NSFileManager defaultManager] removeItemAtPath:fullPath error:&error];
 if (error != nil) {
  DLogErr(@"Unable to remove file: error %@, %@", error, [error userInfo]);
  return; 
 }  

But looking at the documentation It seems like I got this wrong.:

- (BOOL)removeItemAtPath:(NSString *)path error:(NSError **)error

If an error occurs, upon return contains an NSError object that describes the problem. Pass NULL if you do not want error information.

Technically there is no difference between nil and NULL so does this mean I’m actually turning this off and will never get a error message (even if the delete in the above example did fail) ?
Is there a better way to code this ?

Thanks.

  • 1 1 Answer
  • 0 Views
  • 0 Followers
  • 0
Share
  • Facebook
  • Report

Leave an answer
Cancel reply

You must login to add an answer.

Forgot Password?

Need An Account, Sign Up Here

1 Answer

  • Voted
  • Oldest
  • Recent
  • Random
  1. Editorial Team
    Editorial Team
    2026-05-19T05:05:04+00:00Added an answer on May 19, 2026 at 5:05 am

    First off, the following line doesn’t really make sense:

    NSDictionary *attribs = [[NSFileManager defaultManager]
     removeItemAtPath:fullPath error:&error];
    

    -removeItemAtPath:error: returns a BOOL value, not a dictionary.

    I think I see what you’re wondering about with the NULL value. Notice carefully though, how there are 2 *’s in the error parameter in the method signature:

    - (BOOL)removeItemAtPath:(NSString *)path error:(NSError **)error
    

    That means a pointer to a pointer. When you pass in &error, you are passing in the address of the pointer to the NSError. (Ugh, someone else can probably help me out here, as my head still starts to swim when dealing with pointers to pointers). In other words, even though you have set error to nil, you aren’t passing in error to the method, you’re passing in &error.

    So, here’s what the re-written method should look like:

    // If you want error detection:
    NSError *error = nil;
    if (![[NSFileManager defaultManager] removeItemAtPath:fullPath
                error:&error]) {
        NSLog(@"failed to remove item at path; error == %@", error);
        // no need to log userInfo separately
        return;
    }
    
    // If you don't:
    if (![[NSFileManager defaultManager] removeItemAtPath:fullPath
                error:NULL]) {
        NSLog(@"failed to remove item at path");
        return;
    }
    
    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I got into the habit of doing this, so that in my unit tests
I've got into this habit of always using unsigned integers where possible in my
I got into the habit of removing trailing white spaces from my source file.
Me and my colleagues got into this discussion early this morning, and our opinions
I'm not quite sure how I got into this mess, but for some reason
I've got into the habit of using Closures everywhere I can in place of
So I never got into detailed error processing too much when I played in
I got into this learning the Android Operating System. I'm still in learning mode.
Alright well I recently got into normalizing my database for this little side project
I got into an interesting discussion in a forum where we discussed the naming

Explore

  • Home
  • Add group
  • Groups page
  • Communities
  • Questions
    • New Questions
    • Trending Questions
    • Must read Questions
    • Hot Questions
  • Polls
  • Tags
  • Badges
  • Users
  • Help
  • SEARCH

Footer

© 2021 The Archive Base. All Rights Reserved
With Love by The Archive Base

Insert/edit link

Enter the destination URL

Or link to existing content

    No search term specified. Showing recent items. Search or use up and down arrow keys to select an item.