I think the answer to this one might be somewhat obvious...
If you're writing a Cocoa application that alters large groups (or blocks) of strings, will performance be better using NSMutableString (and the substring, range, delete and insert methods), or would I be better off converting the NSString data to char[ ] arrays, performing my manipulations, and then converting it back to NSString for final output?
I already have my functions written in C with character arrays, I'm porting them from the Windows environment. The one problem I see with the char[ ] array approach might be UniCode, however at this time I'm not that concerned with anything outside the bounds of standard ASCII characters. (But I might not want to lock my self into this situation either.)
I will be performing thousands of comparisions and replacements within my strings until an end result is achieved. I'd imagine that you would get better performance using raw C structures, but how do most people handle these types of operations when programming in Cocoa/Objective-C ?