Cheers for the clarification. I will spend some time working through some of
the other failures, should help me get to grips with it all :)
James
Sent from my iPhone
> On 14 May 2016, at 15:02, Bouke Haarsma via swift-corelibs-dev
> wrote:
>
> On 2016-05-14 09:05:08 +, James Lee via swif
Hi David,
> On May 14, 2016, at 1:04 AM, David Hart wrote:
>
> Thanks for all the answers :) These questions are dear to my heart because I
> plan on using corelibs-foundation on Darwin as soon as possible to share code
> between our iOS apps and web services.
Yup, that is exactly the use ca
On 2016-05-14 09:05:08 +, James Lee via swift-corelibs-dev said:
Please excuse my ignorance, I have looked into the POSIX calls, but am
I right in assuming that the EBADF is due to the test calling to a file
that doesn't exist and that is just how OSX handles this case?
The problem on OSX
This does seem to keep more inline with the current Darwin implementation.
Please excuse my ignorance, I have looked into the POSIX calls, but am I right
in assuming that the EBADF is due to the test calling to a file that doesn't
exist and that is just how OSX handles this case?
Cheers for th
The failing testcase is
TestNSTask.test_pipe_stdout_and_stderr_same_pipe. The call to
posix_spawn returns an error code 9 (EBADF).
In order to avoid code repetition I've wrapped all posix calls with a
throwing status code check;
private func posix(_ code: Int32) throws {
switch code {
> On 14 May 2016, at 01:39, Tony Parker wrote:
>
> No. Only on Linux or other non-Darwin platforms.
Ok, I understand that corelibs won't be the official "Foundation" framework on
Darwin, but it will still be available under SwiftFoundation without having to
compile it ourselves right?
_
Thanks for all the answers :) These questions are dear to my heart because I
plan on using corelibs-foundation on Darwin as soon as possible to share code
between our iOS apps and web services.
> On 14 May 2016, at 01:39, Tony Parker wrote:
>
> Over time it’s not clear how the two will evolve,
