how expensive is char* -> NSString?
how expensive is char* -> NSString?
- Subject: how expensive is char* -> NSString?
- From: Scott Andrew <email@hidden>
- Date: Fri, 2 Sep 2005 15:01:15 -0700
I am working on some cross platform code and i am trying to figure
out how to handle a class that has to return strings. This class will
be wrapped inside an objective C object to convert the string to the
NSString in the get acessors and vise versa for set.
The other option if the conversion is very slow and expensive is to
have only sets in the base class and no data representation and the
derive classes will store the correct representation.
So how expensive is it? I already know that the C++ objects have to
be wrapped in an thin objective c wrapper so they can be stored for
use in an ArrayController. I just didn't want to have to duplicate
alot of my HMTL data parsing between Mac and Windows.
Scott
_______________________________________________
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