• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: const correctness
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: const correctness

  • Subject: Re: const correctness
  • From: Jens Alfke <email@hidden>
  • Date: Sat, 17 Mar 2012 22:41:54 -0700
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 (email@hidden)

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:

This email sent to email@hidden
  • Follow-Ups:
    • Re: const correctness
      • From: Luther Baker <email@hidden>
References: 
 >const correctness (From: Luther Baker <email@hidden>)

  • Prev by Date: const correctness
  • Next by Date: Re: const correctness
  • Previous by thread: const correctness
  • Next by thread: Re: const correctness
  • Index(es):
    • Date
    • Thread