When is NSCopying needed?

Question

I know it's needed if your object will be used as a key in an NSDictionary. Are there any other times like this that NSCopying is required?

If I think I don't need my model objects to conform to NSCopying, am I probably wrong?

Indebtedness

Answer 1

When it's being passed to a copy property or any other method that is documented as copying its argument.

Shellacking

Answer 2

Think of the NSCopying protocol as the objective-C version of cloning routines. If a caller was to clone your object, what is the behavior you would want? If your object is solely composed of primitive types, then you don't need to worry about this. But if you have any complex types as members, you might want to clone/copy them instead of passing simple references to them.

Kannan

Answer 3

NSCopying has quite broad usage. Anytime an object owns something it shouldn't share with other objects, you'll need a copy. Mutable objects often need to be copied, though NSMutableCopying might be needed instead of NSCopying.

Mcpeak