Why does NSDictionary report an unusual class name?

NSDictionary *dict = [NSDictionary dic开发者_开发技巧tionary];
NSLog(@"%@", NSStringFromClass([dict class])); 

This code prints "__NSDictionary0".

For my own classes it prints the actual class name.

Why is NSDictionary identified as __NSDictionary0, and is it safe to depend on this?

---

NSDictionary is a class cluster, as Gendolkari said and Class Clusters are documented.

And, no, you can't depend on the exact identity of the private subclass.

You should certainly be able to do the following to determine if it is a dictionary or not:

[myThingaMaHoover isKindOfClass: [NSDictionary class]];

Or, at the least, that it is a dictionary as implemented as a part of the NSDictinoary class cluster.

What you can't do is use isKindOfClass: or isMemberOfClass: to determine whether or not a dictionary (or string, array, or set) is mutable. Consider:

NSDictionary *d = [NSDictionary dictionaryWithObject: [[NSObject new] autorelease] forKey: @"Bob"];
NSMutableDictionary *m = [NSMutableDictionary dictionaryWithObject: [[NSObject new] autorelease] forKey: @"Bob"];
NSLog(@"d class: %@ %@ %@", [d class], [d superclass], [[d superclass] superclass]);
NSLog(@"m class: %@ %@ %@", [m class], [m superclass], [[m superclass] superclass]);

This outputs:

d class: NSCFDictionary NSMutableDictionary NSDictionary
m class: NSCFDictionary NSMutableDictionary NSDictionary

d and m are both instances of NSCFDictionary which inherits from NSMutableDictionary (which inherits from NSDictionary).

---

NSDictionary is a class cluster. Read about them here:

Cocoa Fundamentals Guide

As the "actual" class itself is private, no, it is not safe to depend on this.

If you need to know if your class is really an NSDictionary or not, use [dict isKindOfClass:[NSDictionary class]];

---

So, basically, you need to know if you are having an NSMutableDictionary or a bare NSDictionary beforehand. Or don't need to know. Or create an NSMutableDictionary from your object (NSDictionary or NSMutableDictionary)?

What was the question originally for?

---

If you want to test for mutability, your best bet would probably be conformsToProtocol: @protocol(NSMutableCopying)

---

For an NSDictionary mutability test, could't you just to a 'respondsToSelector' for a method that only an NSMutableDictionary would have, like addObject:ForKey:?