Hi Tony,

we’ve started to change function signature of some of API class. In the 
process, I completed changes to NSFileManager and its dependant code including 
TestFoundation. Here is the pull request for the same 
https://github.com/apple/swift-corelibs-foundation/pull/317 
<https://github.com/apple/swift-corelibs-foundation/pull/317>

- Bhaktavatsal

> Message: 1
> Date: Tue, 12 Apr 2016 09:57:38 -0700
> From: Tony Parker <anthony.par...@apple.com>
> To: Robert F Dickerson <rfdicker...@us.ibm.com>
> Cc: swift-corelibs-dev@swift.org
> Subject: Re: [swift-corelibs-dev] Migrate corelibs-foundation to the
>       newest  APIs
> Message-ID: <02c5d8a5-da42-4579-820e-d2094f264...@apple.com>
> Content-Type: text/plain; charset="utf-8"
> 
> Hi Robert,
> 
> This is something we really do need some help with. Our goal is to have the 
> Linux version match the Darwin version exactly.
> 
> There is also a PR up to change some of the results of the automatic renaming 
> by the importer, here:
> 
> https://github.com/apple/swift/pull/2093 
> <https://github.com/apple/swift/pull/2093>
> 
> So we should take those into account as well.
> 
> - Tony
> 
>> On Apr 12, 2016, at 9:45 AM, Robert F Dickerson via swift-corelibs-dev 
>> <swift-corelibs-dev@swift.org> wrote:
>> 
>> As you know, currently, as of the 03-24 DEVELOPMENT snapshot, the function 
>> signatures for Foundation has diverged. This has caused us to create 
>> platform specific calls to the NSString, NSDate, NSCache, etc. classes. For 
>> instance,
>> 
>> 
>> #if os(Linux)        <ecblank.gif>
>> <ecblank.gif>        let lastSlash = fileName.rangeOfString("/", options: 
>> NSStringCompareOptions.BackwardsSearch)
>> <ecblank.gif>        #else
>> <ecblank.gif>        let lastSlash = fileName.range(of: "/", options: 
>> NSStringCompareOptions.backwardsSearch)
>> <ecblank.gif>        #endif
>> 
>> 
>> I was curious about the timeline for the migration to the newer APIs and 
>> whether someone in particular was working on it. We have some developers 
>> here at IBM@Swift that could do some of this work, but want to make sure we 
>> aren't duplicating work and are coordinated.
>> _______________________________________________
>> swift-corelibs-dev mailing list
>> swift-corelibs-dev@swift.org
>> https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

_______________________________________________
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev

Reply via email to