On 7/17/08 9:55 AM, Jens Alfke said: >> What are my best options to get around that? (Except of using the >> next larger NSNumber variants to store unsigned values in order to >> prevent unwanted sign expensions for unsigned values)? > >Either require 10.5, or use a larger size. The problem is that >NSNumber is just a bridge to CFNumber, which didn't support unsigned >types until 10.5. So on 10.4, the fact that you were storing an >unsigned 32-bit value got lost when you created the NSNumber.
Interesting. What about NSKeyedArchiver? It has, for example, encodeInt32:forKey: but no unsigned equivalent. What should one do if one wants to encode a uint32? Are there sign extension dangers here? Cheers, -- ____________________________________________________________ Sean McBride, B. Eng [EMAIL PROTECTED] Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
