Re: NUL characters in NSString cause unexpected results
Re: NUL characters in NSString cause unexpected results
- Subject: Re: NUL characters in NSString cause unexpected results
- From: Jerry Krinock <email@hidden>
- Date: Thu, 23 Nov 2006 06:49:20 -0500
- Thread-topic: NUL characters in NSString cause unexpected results
on 06/11/22 23:01, Scott Stevenson at email@hidden wrote:
> To be fair, the class reference for NSString is pretty upfront about
> this:
>
> -initWithBytes:length:encoding:
>
> The array must not contain NULL.
Yes, you're right about this Scott. I had assumed that something named
"initWithBytes" would be completely transparent and not bothered to read the
documentation. But indeed, the documentation says otherwise.
This explains the whole issue, at least for NSString.
on 06/11/23 2:09, Rosyna at email@hidden wrote:
> That's odd since it just calls CFStringCreateWithBytes() and
> CFStringCreateWithBytes() has no such note. Bizarre.
I believe you're correct, Rosyna, so I just submitted an "It wasn't helpful"
report regarding documentation of CFStringCreateWithBytes().
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden