Re: Core Data, dynamic accessors and compiler warnings
Re: Core Data, dynamic accessors and compiler warnings
- Subject: Re: Core Data, dynamic accessors and compiler warnings
- From: Jim Correia <email@hidden>
- Date: Sun, 10 Aug 2008 10:13:29 -0400
On Aug 10, 2008, at 10:02 AM, Chris Idou wrote:
The Core data doco suggests that if you have a 1:M accessor for
FooBar that you define in a header:
- (void)addFooBarObject:(FooBar *)value;
In order to suppress compiler warnings for using this dynamically
generated method. However this creates its own "incomplete
implementation" compiler warning for the class.
(Actually the doco uses a category rather than a class, but the
principle should be the same).
Do what the documentation suggests, and you'll avoid the warning.
That is, declare your dynamic accessor methods on a category which has
no matching @implementation.
Jim
_______________________________________________
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