Re: create NSMutableString with no limit?
Re: create NSMutableString with no limit?
- Subject: Re: create NSMutableString with no limit?
- From: themacuser <email@hidden>
- Date: Sun, 19 Mar 2006 13:06:10 +1030
On 19/03/2006, at 11:41 AM, Boyd Collier wrote:
Just a small cautionary note: the capacity you specify doesn't
assure you that you can do what might seem reasonable,
or at least that's been my experience. For example,
NSMutableString *myMutableString = [NSMutableString
stringWithCapacity:10];
NSLog(@" the length of myMutableString is %i", [myMutableString
length]);
[ myMutableString insertString:@"this is junk" atIndex:3];
How is that reasonable? You're inserting a string into a string of
length 0, at 3. That's outside the string's boundary
produces this in the Run Log:
2006-03-18 16:54:54.561 SuperSpagedi[968] the length of
myMutableString is 0
2006-03-18 16:54:54.581 SuperSpagedi[968] *** -[NSCFString
insertString:atIndex:]: Range or index out of bounds
But the following works
NSMutableString *myMutableString = [NSMutableString
stringWithCapacity:10];
NSLog(@" the length of myMutableString is %i", [alleleString
length]);
// [myMutableString insertString:@"this is junk" atIndex:3];
[myMutableString appendString:@"this is junk"];
[myMutableString insertString:@"worthless " atIndex:8];
NSLog(@"here is myMutableString %@ ", myMutableString);
However, this is within the string's boundary. The capacity of the
string is being automatically extended here when there's too much on
the string.
Boyd
On Mar 18, 2006, at 2:46 PM, Paul Lynch wrote:
On 18 Mar 2006, at 22:37, James W. Walker wrote:
What's the right way to create an NSMutableString with no limit
on its capacity? The only initialization method listed in the
docs is initWithCapacity, and it doesn't say you can pass 0 as
the capacity. I can take advantage of toll-free bridging and say
(NSMutableString*)CFStringCreateMutable( NULL, 0 ), but there
must be a more obvious way.
Capacity is not a limit; it is a hint. So use any number you feel
like. Zero might even work; I haven't tried.
I notice that there is a potential conflict in the descriptions of
NSMutableString and CFStringCreateMutable in the way that capacity
is described.
Paul
_______________________________________________
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