Am 17.07.2008 um 18:55 schrieb Jens Alfke:
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.
Thanks for confirming. I'll probably end up writing enhancement
requests to documentation so this behavior gets documented.
I can't demand Leopard in that case as it's a Tiger-targeting PTP
implementation working around some Image Capture shortcomings.
It ran into pretty some problems mixing and matching my stored (int
based) key-value lookup tables with camera returned (uint16) values
after switching from (Leopard only) prototype to an Tiger SDK
"elaborated prototype"..
Best Regards,
Tom_E
_______________________________________________
Cocoa-dev mailing list ([email protected])
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]
