keyed archiving questions
keyed archiving questions
- Subject: keyed archiving questions
- From: Alex Rice <email@hidden>
- Date: Tue, 5 Nov 2002 21:58:53 -0700
1) I've started using keyed archives and it's so much cleaner, I really
don't want to maintain any classes to continue to use non-keyed
NSArchiving/NSCoding in encodeWithCoder:. Would it be stupid to require
10.2 for the next release of my app? What's the adoption rate of 10.2?
How many other developers are maintaining pre-10.2 compatibility when
adding new features in their encodeWithCoder: methods?
2) In "compatibility strategies for keyed archives" there is an item:
"Allow for 64-bit integers. Someday, your class's code may run on a
machine with a processor with a 64-bit native word size."
(like next year eh? wink wink nudge nudge)
I was thinking about just starting today to use -encodeInt64:forKey:
and -decodeInt64ForKey:, but then I was thinking maybe I should just
start using NSNumber instead and then won't have to deal with this
issue again when processors jump from 64 to 128 bits. Or is NSNumber
serialization going to have issues as well when moving from 32 to 64
bits? Performance is not really an issue. What do you think? Just use
NSNumber?
TIA
Alex Rice <email@hidden>
Mindlube Software
http://mindlube.com/
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.