On Mon, Aug 18, 2008 at 7:38 AM, Jason Coco <[EMAIL PROTECTED]> wrote:
>
> On Aug 18, 2008, at 10:18 , Clark Cox wrote:
>
>> On Mon, Aug 18, 2008 at 5:38 AM, Jason Coco <[EMAIL PROTECTED]> wrote:
>>>
>>> On Aug 18, 2008, at 07:18 , Robert Černý wrote:
>>>
>>>> Actually,I'm trying to debug some weird problems with clipboard. My
>>>> problem
>>>> is that data copied into clipboard from legacy java application doesn't
>>>> match data pasted into Cocoa application. I've got data with accented
>>>> characters which gets converted through MacOS Roman encoding even the
>>>> visual
>>>> representation in java is correct.
>>>
>>>
>>> If you want to print the string as hexadecimal without any conversions,
>>> you
>>> can do
>>> something like the following (keep in mind this is showing you basically
>>> the
>>> UCS-2 version of the string):
>>
>> Not UCS-2, UTF-16. (The distinction is important if the string
>> contains any characters outside of the BMP.
>
> Yeah, my bad... UTF-16, not UCS-2
>
>>> void dumpString(NSString *str)
>>> {
>>> NSUInteger len = [str length];
>>> unichar *chars = malloc(len * sizeof(unichar));
>>> [str getCharacters:chars];
>>> uint i;
>>
>> i should be NSUInteger as well.
>
> I don't think that really matters all that much, just a matter of
> style mostly. I think /should/ is strong. It could be NSUInteger
> or just int or uint32_t or unsigned int or whatever...
If the length is an NSUInteger, then the counter should be as well.
> it's just a counter for a simple debugging example, right :)
Indeed, but unless there's a good reason, using different types for
the index and the limit is not a good idea.
>
>>> printf("NSString at %08p = { ", str);
>>
>> No need to use %08p, just use %p.
>
> I wanted %08p... it was on purpose. I like my debugging messages
> to line up properly :)
Then what happens when you build 64-bit? :)
--
Clark S. Cox III
[EMAIL PROTECTED]
_______________________________________________
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]
