• 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: Calling getter on const object
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Calling getter on const object


  • Subject: Re: Calling getter on const object
  • From: David Duncan <email@hidden>
  • Date: Mon, 8 Nov 2010 08:53:46 -0800

My question is why do you need to have a 'const' pointer.

On Nov 8, 2010, at 8:37 AM, Jonny Taylor wrote:

> I'm afraid I'm not sure if I understand exactly what you're asking. I would like to be able access the "frame number" property (which is in fact stored as a variable within the class, and is fixed soon after instantiation) in spite of the fact that I only have a 'const' pointer to the object at the time I want to access it. Semantically I don't see why it should be unsafe to attempt to find out the value of that property.

--
David Duncan

_______________________________________________

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: Calling getter on const object
      • From: Jonny Taylor <email@hidden>
References: 
 >Calling getter on const object (From: Jonny Taylor <email@hidden>)
 >Re: Calling getter on const object (From: David Duncan <email@hidden>)
 >Re: Calling getter on const object (From: Jonny Taylor <email@hidden>)

  • Prev by Date: Re: Calling getter on const object
  • Next by Date: RE: Ping host and port
  • Previous by thread: Re: Calling getter on const object
  • Next by thread: Re: Calling getter on const object
  • Index(es):
    • Date
    • Thread