• 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: @dynamic and Programmatic Access to Setters
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: @dynamic and Programmatic Access to Setters


  • Subject: Re: @dynamic and Programmatic Access to Setters
  • From: Quincey Morris <email@hidden>
  • Date: Thu, 17 Apr 2008 22:07:26 -0700


On Apr 17, 2008, at 20:15, Mike Rossetti wrote:

Then I add a class method that creates a new Tip and tries the following assignment (two approaches shown):

  newTip.tipName = @"FUBAR";
  [newTip setTipName:@"FUBAR"];

It would be interesting to know if, at the point of the error, the getter failed as well as the setter.


It would be interesting to know if [newTip setValue:@"FUBAR" forKey:@"tipName"] also failed.

It would be interesting to know if the setter fails on fetched (existing) Tips, or just on newly created ones.

Both cause a runtime error:

-[tip setTipName:]: unrecognized selector sent to instance


Is that the exact error message, or is it [Tip setTipName]? "tip" seems inexplicable.


_______________________________________________

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


References: 
 >@dynamic and Programmatic Access to Setters (From: Mike Rossetti <email@hidden>)

  • Prev by Date: Re: Unregistering KVO observers
  • Next by Date: Re: @dynamic and Programmatic Access to Setters
  • Previous by thread: Re: @dynamic and Programmatic Access to Setters
  • Next by thread: Re: @dynamic and Programmatic Access to Setters
  • Index(es):
    • Date
    • Thread