unichar and NSString – how interchangeable are these?

You have two options: the first is a category adding a stringWithUnichar method to NSString:

@interface NSString (MNNSStringWithUnichar)
+ (NSString *) stringWithUnichar: (unichar) value;
@end


@implementation NSString (MNNSStringWithUnichar)

+ (NSString *) stringWithUnichar:(unichar) value {
     NSString *str = [NSString stringWithFormat: @"%C", value];
     return str;
}

@end

Then call it with

NSString *otherString = @"TestString";

NSString *str = [NSString stringWithUnichar:[otherString characterAtIndex:1]];

or you could just directly go like this:

NSString *str = [NSString stringWithFormat:@"%C",[otherString characterAtIndex:1]];

Choose the category if you want to use it repeatedly, or if you only have to do it once, use the stringWithFormat example!!

Not to sure about the internals of NSString, but I’d guess it is probably wrapping a

unichar *

or an array of unichars (like a C char *)

A unichar is simply a 16bit value that is used to store a character. Unlike an unsigned char which is only 8 bits, it can hold more than 0-255, so it can hold unicode characters as well, which are 16bits. A NSString is a (cluster of) class[es] that contains an array of unichars

EDIT

Here are a few articles about what people think an NSString is:

http://cocoawithlove.com/2008/08/string-philosophies-char-arrays.html

String philosophies: char arrays, std::string and NSString
by inprogramming

Leave a Comment

Hata!: SQLSTATE[HY000] [1045] Access denied for user 'divattrend_liink'@'localhost' (using password: YES)