> On Aug 13, 2015, at 13:08 , Quincey Morris
> <quinceymor...@rivergatesoftware.com> wrote:
>
> On Aug 13, 2015, at 12:56 , Rick Mann <rm...@latencyzero.com> wrote:
>>
>> Now I have to write:
>>
>> let s2 = ((s as NSString).stringByExpandingTildeInPath as
>> NSString).stringByAppendingPathComponent("foo")
>>
>> How is this better?
>
> What happened is that the methods in NSPathUtilities.h are no longer
> available to the String type. It’s unknown whether this was an oversight, or
> if there’s a philosophical reason for the change. I guess we’ll find out in
> the next beta.
>
> In the meantime, casting to NSString is a slight inconvenience, or you can
> use NSURL (though Charles Strska has pointed out that you need to be careful
> when appending a path extension to a NSURL).
I guess what I was getting at was, perhaps it makes more sense for the NSString
extension methods to return NSString, rather than String.
--
Rick Mann
rm...@latencyzero.com
_______________________________________________
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
