On 7 Mar 2017, at 18:00, Jens Alfke <j...@mooseyard.com> wrote: > > On Mar 7, 2017, at 8:13 AM, davel...@mac.com wrote: >> >> NSFileManager *fm = [[NSFileManager alloc] init]; >> const char *data = [name fileSystemRepresentation]; >> NSString *filename = [fm stringWithFileSystemRepresentation:data >> length:strlen(data)]; > > This is a no-op, since you’re calling two methods that perform inverse > operations — `filename` will end up being identical to `name`.
AFAIK it isn’t a no-op (at least at present). Right now, I rather suspect it’ll lead to decomposition and the replacement of Hangul characters in the range U+AC00 through U+D7A3, according to the rules in TN1150. Unfortunately, because -fileSystemRepresentation doesn’t really know the underlying filesystem, this may or may not be appropriate, and I’d expect *in future* at some point the above really will be a no-op as a result. Kind regards, Alastair. -- http://alastairs-place.net _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
