On Jun 17, 2011, at 04:19, Andreas Grosam wrote: > It does not convert at all. It can understand any Unicode encoding form, > though.
Ah, OK, I misunderstood you to mean "parsing" in relation to the Unicode representation itself. That's not as silly as it sounds, because it's not entirely trivial to decode UTF-8 or UTF-16 with robust error detection and recovery. > However, if I have to deal with "very large input", I guess NSString is no > option anyway, not only for performance reasons, but also from a memory > foot-print perspective( IFF my current understanding of NSString is correct, > namely that its content is stored in memory). I think you just answered your own (original) question: you shouldn't be considering NSString input at all. Instead, you should be retrieving data from all significantly-sized input sources in raw form. That doesn't mean you shouldn't *accept* NSString input, just that you shouldn't waste time on performance optimizations of NSString input. :) _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please 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: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
