That makes sense ... although the compiler sure does a good job of catching it at compile time :)
I was ruminating about it more of a (self) documenting angle as opposed to runtime enforcement ... and indeed, its application in C++ is what I'm was thinking of. Thanks Jens! -Luther On Sun, Mar 18, 2012 at 12:41 AM, Jens Alfke <j...@mooseyard.com> wrote: > > On Mar 17, 2012, at 10:12 PM, Luther Baker wrote: > > Just curious for the reasoning as to why some of the API calls like > [NSDictionary valueForKey:] take an NSString* and not a *const* NSString* ? > > > ‘const’ doesn’t mean anything when applied to Objective-C object pointers. > Unlike C++, the language has no notion of a const versus a non-const > pointer to an object. (There’d be no way to enforce it anyway, since you > can send any message to any object.) > > —Jens > > _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
