Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
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.
So, I’m making an iPhone app in Objective-C and need to use an array. Usually in Objective-C I’d use NSArray or NSMutableArray, but I’m starting to wonder if that’s the best idea when simply using a basic array. Memory- and efficiency-wise, does it make more sense to use a regular C array or an Objective-C array when simply keeping a basica array of custom objects? And do you usually use C arrays or Objective-C arrays when programming in Objective-C? Thanks!
This really just depends on what you want to do with the array.
For arrays of numbers that you’re going to do lots of math on, C arrays are probably a better choice (or at least a class that wraps C arrays). If you’re constantly converting back and forth between scalars and objects and aren’t using any of NSArray’s more advanced features, all it will buy you is a lot of overhead.
However, Cocoa objects have a number of memory management invariants that you must obey or your app will go boom. C arrays and C++ vectors will blissfully ignore these requirements, meaning a lot more work for you to keep them in line. NSArray will take care of these for you. When you’re dealing with Cocoa objects, use an NSArray.