Re: dumb NSLog question
Re: dumb NSLog question
- Subject: Re: dumb NSLog question
- From: Kevin Ballard <email@hidden>
- Date: Sun, 8 Jan 2006 22:15:36 -0800
Actually that shouldn't be the case at all. You don't want the null
byte to be in the NSString itself, so a length of 3 is correct.
No, I think it's more likely that, for whatever reason, NSLog isn't
outputting anything unless it has at least one ASCII character, and
setting a length of 4 works because the null byte after the (tm) char
is enough to make NSLog display the output.
Perhaps you should file a bug on this?
On Jan 8, 2006, at 5:27 PM, Lester Dowling wrote:
'Tis the bletcherous bug of wrong length.
Change the length from 3 to 4:
NSString *tmChar = [[NSString alloc] initWithBytes:"\xE2\x84\xA2"
length:4 // Include the terminating null.
encoding:NSUTF8StringEncoding
];
Now it works without making hey:
2006-01-09 12:26:21.306 tmlog[537] ™
--
Kevin Ballard
email@hidden
http://www.tildesoft.com
http://kevin.sb.org
Attachment:
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden