• 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: Core data accessors for structs
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Core data accessors for structs


  • Subject: Re: Core data accessors for structs
  • From: MH <email@hidden>
  • Date: Tue, 26 Jun 2007 07:21:09 +0100

What is the best way to encode a struct so as to obtain persistence using
the Core Data framework, and avoid the pitfalls mentioned?

Should I be following the non-object guidelines supplied by Apple, and use
shadow attributes? This doesn't seem to address the problem mentioned by
Jim:

If you serialize structures in this way, you won't be able to read
them back on a different architecture (little endian vs. big endian,
32 vs. 64 bit, different structure padding rules, etc.)
_______________________________________________

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 accessors for structs
      • From: Jim Correia <email@hidden>
References: 
 >Core data accessors for structs (From: MH <email@hidden>)
 >Re: Core data accessors for structs (From: Charles Steinman <email@hidden>)

  • Prev by Date: Re: AppleScript not sending my Cocoa app proper floats on Intel
  • Next by Date: Re: AppleScript not sending my Cocoa app proper floats on Intel
  • Previous by thread: Re: Core data accessors for structs
  • Next by thread: Re: Core data accessors for structs
  • Index(es):
    • Date
    • Thread