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

  • Home
  • SEARCH
  • 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 721019
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Editorial Team
Asked: May 14, 20262026-05-14T05:49:30+00:00 2026-05-14T05:49:30+00:00

I know you shouldn’t use this to decide whether or not to change an

  • 0

I know you shouldn’t use this to decide whether or not to change an array:

if ([possiblyMutable isKindOfClass:[NSMutableArray class]])

But say I’m writing a method and need to return either an NSMutableArray or an NSArray, depending on the mutability of possiblyMutable. The class using my method already knows whether or not it’s acceptable to change the returned array. Whether or not it’s acceptable to change the returned array directly correlates with whether or not it’s acceptable to change possiblyMutable.

In that specific case, is this code safe? It seems to me that if it’s not acceptable to change the array, but we accidentally get a mutable array, it’s ok, because the class using my method won’t try to change it. And if it is acceptable to change the array, then we will always get possiblyMutable as an NSMutableArray (though this is the part I’m not entirely clear on).

So… safe or not? Alternatives?

  • 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-14T05:49:30+00:00Added an answer on May 14, 2026 at 5:49 am

    No. Not safe at all.

    If you do:

    NSMutableArray * ma = [NSMutableArray arrayWithObject:@"foo"];
    NSArray * aa = [NSArray arrayWithObject:@"foo"];
    
    NSLog(@"Mutable: %@", [ma className]);
    NSLog(@"Normal: %@", [aa className]);
    

    Then you get:

    2010-04-05 13:17:26.928 EmptyFoundation[55496:a0f] Mutable: NSCFArray
    2010-04-05 13:17:26.956 EmptyFoundation[55496:a0f] Normal: NSCFArray

    You also can’t do:

    NSLog(@"Mutable add: %d", [ma respondsToSelector:@selector(addObject:)]);
    NSLog(@"Normal add: %d", [aa respondsToSelector:@selector(addObject:)]);
    

    Because this logs:

    2010-04-05 13:18:35.351 EmptyFoundation[55525:a0f] Mutable add: 1
    2010-04-05 13:18:35.351 EmptyFoundation[55525:a0f] Normal add: 1

    The only ways to guarantee you have a mutable array are to take the -mutableCopy of an existing array or if the return type of a function/method guarantees the array will be mutable.

    • 0
    • Reply
    • Share
      Share
      • Share on Facebook
      • Share on Twitter
      • Share on LinkedIn
      • Share on WhatsApp
      • Report

Sidebar

Related Questions

I know this shouldn't be that hard, but I couldn't find the answer on
This is one of those I know I shouldn't do this but it's oh
I know this should be simple and I should know it but it's eluding
I feel like I should know this, but I haven't been able to figure
I get the feeling this is probably something I should know but I can't
I know I shouldn't be outputting things directly in PHP, but using a template
I know I shouldn't be exposing a List<T> in a property, but I wonder
I know destructor shouldn't not throw exception. http://www.parashift.com/c++-faq-lite/dtors.html#faq-11.13 I have the following code :
I know I shouldn't have id's with the same value. This is just fictitious,
I am trying to wrap my head around this problem. I know views shouldn't

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.