>
>>> <given some start address in an unsigned char [] buffer = 0xnnnn>
>> Doesn't necessarily work quite that simply with Unicode and NSString and its
>> family.
>> From a file that is ASCII data you could create a C array like that ...
>
> Huh? William didn’t say anything about where the data came from. As long as
> it’s already in a C byte array (or an NSData) it can be displayed as a hex
> dump pretty easily.
Ah! Forgot about NSData. But all I saw was it likely coming out of
NSTextStorage meaning an NSAttributedString. I wasn't seeing that going
*reliably* into unsigned char [] buffer.
I would think it safer to ensure encoding things were covered.
>
>> Are you sure it is ASCII ...?
>> Internally to NSString and friends it likely is not. It's best to forget
>> much of what you think you know in assuming things are ASCII.
>
> Again, this has nothing to do with NSString. I think you’re off base here.
I May have read more into it than is there, but I was thinking it as not
necessarily enough space for what may be in the backing store of the textView.
Probably in that I'm always working with things where I do have to remind
people that everything isn't in ASCII.
I've been up too long with not enough sleep...
_______________________________________________
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:
https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [email protected]
