• 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
Core Data, dynamic accessors and compiler warnings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Core Data, dynamic accessors and compiler warnings


  • Subject: Core Data, dynamic accessors and compiler warnings
  • From: Chris Idou <email@hidden>
  • Date: Sun, 10 Aug 2008 07:02:41 -0700 (PDT)

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).

How do I suppress compiler warnings for core-data 1:M accessors with custom classes?






_______________________________________________

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: Core Data, dynamic accessors and compiler warnings
      • From: Jim Correia <email@hidden>
  • Prev by Date: Core Data versioning woes
  • Next by Date: Re: Core Data, dynamic accessors and compiler warnings
  • Previous by thread: Re: Core Data versioning woes
  • Next by thread: Re: Core Data, dynamic accessors and compiler warnings
  • Index(es):
    • Date
    • Thread