• 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
Getting rid of primitive accessor warnings
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Getting rid of primitive accessor warnings


  • Subject: Getting rid of primitive accessor warnings
  • From: Rick Mann <email@hidden>
  • Date: Wed, 31 Oct 2012 21:02:39 -0700

I'm not sure what's going on here. But I've got an iOS project that declares (but does not define) some "primitiveFoo" methods in my NSManagedObject subclass, and an OS X project that does so as well. However, the iOS project doesn't emit any warnings, while the OS X project does.

PartDefinition.mm:45:17: Incomplete implementation
PartDefinition.mm:36:1: Method definition for 'primitivePins' not found

Also, when I generated the NSManagedObject subclass from the model, it didn't generate the primitive accessor declarations the way older Xcodes did. Am I doing something wrong?

--
Rick




_______________________________________________

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

  • Prev by Date: Re: Programmatically providing default value for new core data attribute?
  • Next by Date: Re: ARC question
  • Previous by thread: Re: Drawing customized window
  • Index(es):
    • Date
    • Thread