• 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: setValue vs setObject (NSMutableDictionary)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: setValue vs setObject (NSMutableDictionary)


  • Subject: Re: setValue vs setObject (NSMutableDictionary)
  • From: Mark Dawson <email@hidden>
  • Date: Sun, 17 Apr 2005 17:36:47 -0700

Why would you expect that to work? -setValue:forKey: is clearly documented as taking an id for value.

The difference is that setValue is KVC compliant, whereas setObject was not.

Sorry about that. I could have sworn that I saw something that referenced it could be a scalar (which is why I asked the question), but all I see now is the (id) reference. SIgh.

Thanks,

mark

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: setValue vs setObject (NSMutableDictionary)
      • From: Sherm Pendley <email@hidden>
References: 
 >setValue vs setObject (NSMutableDictionary) (From: Mark Dawson <email@hidden>)
 >Re: setValue vs setObject (NSMutableDictionary) (From: Sherm Pendley <email@hidden>)

  • Prev by Date: Help for Buttons
  • Next by Date: indeterminate progress bar animation problem
  • Previous by thread: Re: setValue vs setObject (NSMutableDictionary)
  • Next by thread: Re: setValue vs setObject (NSMutableDictionary)
  • Index(es):
    • Date
    • Thread