• 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
NSData and endianness
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

NSData and endianness


  • Subject: NSData and endianness
  • From: "ad veloper" <email@hidden>
  • Date: Wed, 18 Jul 2007 12:51:43 +0100

List,

Which is the most reliable and forward compatible method for the
encoding of a c-style array as an NSData object for use in Core Data?

Currently I'm using an NSMutableData object with:

"- (void)appendBytes:(const void *)bytes length:(unsigned)length" to
incrementally build the NSData object as I interate the c-style array.

I'm wary of endianness issues, but unsure as to whether or not they
apply in this situation?

This situation is roughly this:

1. myApp converts existing fileformats to produce a series of c-style arrays
2. myApp encodes arrays as NSData objects to store as CoreData attributes.

Thanks.
_______________________________________________

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: NSData and endianness
      • From: David Duncan <email@hidden>
    • Re: NSData and endianness
      • From: Nick Zitzmann <email@hidden>
  • Prev by Date: Re: NSScreen + resolution change
  • Next by Date: Re: NSScreen + resolution change
  • Previous by thread: Re: NSProgressIndicator (CallBacks)
  • Next by thread: Re: NSData and endianness
  • Index(es):
    • Date
    • Thread