Re: [swift-corelibs-dev] NSTask and NSFileHandle implementation
Hi Dan: The Dispatch sources are mostly complete - unfortunately DISPATCH_SOURCE_TYPE_PROC isn't there and it unlikely to be there in a hurry. It would ideally need the underlying kqueue library to have EVFILT_PROC support, which it doesn't today. Chris From: Dan Stenmark via swift-corelibs-dev To: Alexander Alemayhu Cc: Swift core libraries Date: 16/04/2016 22:00 Subject:Re: [swift-corelibs-dev] NSTask and NSFileHandle implementation Sent by:swift-corelibs-dev-boun...@swift.org While we’re on the subject, I’ve been out of the loop for a little while: how’s the Linux-side implementation of dispatch sources looking these days? In particular, I’m interested in the status of DISPATCH_SOURCE_TYPE_READ and DISPATCH_SOURCE_TYPE_PROC. Right now, NSTask is using Good Ol’ CFRunLoops for it’s event handling, and I’d really like to move that over to GCD as soon as I can. Dan On Apr 16, 2016, at 1:55 PM, Dan Stenmark wrote: Hey Alexander, I supplied most of the initial implementation of NSTask, but was holding off on IO redirection until someone tackled NSFileHandle. I can’t say if anyone else on this list is working on this right now, but if not and if you’re really interested in finishing NSFileHandle, I would (very happily!) take care of the relevant implementation in NSTask. Dan On Apr 16, 2016, at 1:50 AM, Alexander Alemayhu via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: Hei Everyone, Is anyone working on the NSTask and/or NSFileHandle implementation? I would like to fix the hangs issue in order to revert [3aa8434][0](disable NSTask tests for now since it can cause hangs., 2016-01-21), but want to avoid duplicating work. Fixing this should also resolve [SR-625][1]. Thanks. [0]: https://github.com/apple/swift-corelibs-foundation/commit/3aa8434df50d9513a0ac1646fb52516a092fa728 [1]: https://bugs.swift.org/browse/SR-625 -- Mit freundlichen Grüßen Alexander Alemayhu ___ 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 ___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
Re: [swift-corelibs-dev] Crypto as part of the core libraries
Hi Travis: FYI, Security (crypto/secure transport etc) is an area that some of us from IBM are just starting to look at. We've love to collaborate with you on it. Chris From: Travis Beech via swift-corelibs-dev To: Tony Parker Cc: "swift-corelibs-dev@swift.org" Date: 15/04/2016 17:19 Subject:Re: [swift-corelibs-dev] Crypto as part of the core libraries Sent by:swift-corelibs-dev-boun...@swift.org I guess I need to RTFM the docs on the swift evolution process. I’ll start there. :-) Travis Beech | Principal Developer | Unwired Revolution | c: 1 (209) 535-5357 Optimizing Operations for Mobile and Distributed Systems From: on behalf of Travis Beech via swift-corelibs-dev Reply-To: Travis Beech Date: Friday, April 15, 2016 at 9:12 AM To: Tony Parker Cc: "swift-corelibs-dev@swift.org" Subject: Re: [swift-corelibs-dev] Crypto as part of the core libraries Tony, I would be more than happy to step and lead the project as security in general is something that I’m very passionate about. Travis Beech | Principal Developer | Unwired Revolution Optimizing Operations for Mobile and Distributed Systems From: on behalf of Tony Parker < anthony.par...@apple.com> Date: Friday, April 15, 2016 at 9:10 AM To: Travis Beech Cc: "swift-corelibs-dev@swift.org" Subject: Re: [swift-corelibs-dev] Crypto as part of the core libraries Hi Travis, Someone will need to step up and lead the project. Is that you? =) Personally, I’m hoping that the structure of the Swift Package Manager will really encourage people to create new frameworks, and give them the tools they need to distribute for use by many developers. That will be a great incubation area for these kinds of ideas. - Tony On Apr 15, 2016, at 9:04 AM, Travis Beech wrote: Tony, How is that achieved? Or what kicks off that community-driven process? Travis Beech | Principal Developer | Unwired Revolution Optimizing Operations for Mobile and Distributed Systems From: on behalf of Tony Parker < anthony.par...@apple.com> Date: Friday, April 15, 2016 at 9:02 AM To: Travis Beech Cc: "swift-corelibs-dev@swift.org" Subject: Re: [swift-corelibs-dev] Crypto as part of the core libraries Hi Travis, I think the best path for projects to become part of the corelibs “umbrella” is to start them off as community-driven, and once they have gained enough momentum we should consider folding them into the core distribution. This provides a lot of key benefits. Most importantly, the new project will have clear ownership and responsibility. We need to make sure that the right people are there to represent its interests to the larger Swift effort. Also, we’ll know who to talk to to deal with general issues like keeping it up to date with language changes, integrating it with CI, considering API changes, etc. - Tony On Apr 14, 2016, at 3:53 PM, Travis Beech via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: I would like to propose that basic crypto be part of the core libraries of swift. It seems a large oversight that this isn’t a core part of the runtime. Many if not all modern languages provide the ability to perform hashing, encryption, certificates, etc. out of the box. I believe that any serious app developer should be encrypting their customer’s data client side; and with the Swift runtime today, I cannot write a pure Swift app without having to resort to bridging into the CommonCrypto C library. While this works, in my view, this is a hack used to bridge the gap of missing functionality. I also don’t think developers should be using libraries they find out on Github or other places. While the developers of those projects may have the best of intentions, I think it best that functionality of this sort come from the language runtime itself, that is part of the core libraries out of the box. As Swift looks to move beyond just iOS/OS X, crypto will become an ever increasingly important aspect of the core libraries such AES and RSA encryption, HMAC SHA1/256 hashing, etc. Thank you, Travis Beech | Principal Developer | Unwired Revolution Optimizing Operations for Mobile and Distributed Systems ___ 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 ___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
Re: [swift-corelibs-dev] NSTask and NSFileHandle implementation
Hi Daniel: Support for DISPATCH_SOURCE_TYPE_READ should be there. If I remember correctly its just support for processes and VM memory pressure that isn't available. Chris From: Daniel Eggert To: Chris Bailey/UK/IBM@IBMGB Cc: Dan Stenmark , Swift core libraries Date: 20/04/2016 02:46 Subject:Re: [swift-corelibs-dev] NSTask and NSFileHandle implementation Wouldn't it still be a huge win to use dispatch for reading from / writing to a file descriptor? /Daniel On Apr 18, 2016, at 01:52, Chris Bailey via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: Hi Dan: The Dispatch sources are mostly complete - unfortunately DISPATCH_SOURCE_TYPE_PROC isn't there and it unlikely to be there in a hurry. It would ideally need the underlying kqueue library to have EVFILT_PROC support, which it doesn't today. Chris From:Dan Stenmark via swift-corelibs-dev < swift-corelibs-dev@swift.org> To:Alexander Alemayhu Cc:Swift core libraries Date:16/04/2016 22:00 Subject:Re: [swift-corelibs-dev] NSTask and NSFileHandle implementation Sent by:swift-corelibs-dev-boun...@swift.org While we’re on the subject, I’ve been out of the loop for a little while: how’s the Linux-side implementation of dispatch sources looking these days? In particular, I’m interested in the status of DISPATCH_SOURCE_TYPE_READ and DISPATCH_SOURCE_TYPE_PROC. Right now, NSTask is using Good Ol’ CFRunLoops for it’s event handling, and I’d really like to move that over to GCD as soon as I can. Dan On Apr 16, 2016, at 1:55 PM, Dan Stenmark wrote: Hey Alexander, I supplied most of the initial implementation of NSTask, but was holding off on IO redirection until someone tackled NSFileHandle. I can’t say if anyone else on this list is working on this right now, but if not and if you’re really interested in finishing NSFileHandle, I would (very happily!) take care of the relevant implementation in NSTask. Dan On Apr 16, 2016, at 1:50 AM, Alexander Alemayhu via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: Hei Everyone, Is anyone working on the NSTask and/or NSFileHandle implementation? I would like to fix the hangs issue in order to revert [3aa8434][0](disable NSTask tests for now since it can cause hangs., 2016-01-21), but want to avoid duplicating work. Fixing this should also resolve [SR-625][1]. Thanks. [0]: https://github.com/apple/swift-corelibs-foundation/commit/3aa8434df50d9513a0ac1646fb52516a092fa728 [1]: https://bugs.swift.org/browse/SR-625 -- Mit freundlichen Grüßen Alexander Alemayhu ___ 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 ___ 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
[swift-corelibs-dev] Use of pthread_main_np() in NSOperation
NSOperation.swift currently makes a call to pthread_main_np() on line 536.
This causes a compilation failure on Linux as there isn't an
implementation of pthread_main_np() in Glibc.
There's few ways of fixing this. Before I go ahead and implement one of
them, I'd like to get some input on what we thing is the best approach.
The most obvious approach would be to leverage the shim we've added to
CoreFoundation already. We implemented pthread_main_np() using the
following function in CFPlatform.c:
Boolean _CFIsMainThread(void) {
return syscall(SYS_gettid) == getpid();
}
This is only available internally to CF, but could be exposed to
Foundation, either as _CFIsMainThread() or as pthread_main_np().
Other options would be to expose the pthread_main_np() shim that's in
Dispatch already (again internally), or to add it to the Glibc overlay so
its available globally.
Any thoughts on the best approach?
Chris___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
Re: [swift-corelibs-dev] libdispatch on Linux, or C++ std::async?
I'd certainly recommend picking up the experimental/foundation branch as Rob recommends. Its where we've been doing some additional work to get properly built into the Swift toolchain and to open up some internal APIs needed by Foundation. Whilst I've been building Dispatch either independently or as part of a full toolchain using the buildbot_linux preset (with dispatch and install-dispatch added), I've just checked your build line and its working fine for me. It might be worth cleaning out any partial build you might have of libdispatch in your build directory, and running 'make distclean' from your libdispatch source directory. FYI, we've got some further changes to the experimental/foundation branch of libdispatch with should land in the next couple of days. This fixes some issues with the Swift overlay, and resolves a crash that we've found in the underlying libkqueue implementation. Chris From: Rob Allen via swift-corelibs-dev To: Brian Gesiak Cc: Swift Core Libs Date: 30/05/2016 08:08 Subject:Re: [swift-corelibs-dev] libdispatch on Linux, or C++ std::async? Sent by:swift-corelibs-dev-boun...@swift.org Hi, For what it's worth, I can't get the master branch to build either, but I can get the experimental/foundation branch to build. Regards, Rob On 30 May 2016, at 05:28, Brian Gesiak via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: Hello all! I'm working on https://bugs.swift.org/browse/SR-710, which involves porting SourceKit to Linux. SourceKit contains a handful of references to libdispatch symbols. I have two questions: 1. Could someone share a set of instructions to build swift-corelibs-libdispatch on Linux? I'm using Ubuntu 15.10 and have installed [the dependencies listed here]( https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20151207/000122.html ). I have tried using both `swift/utils/build-script --libdispatch` as well as the instructions in the swift-corelibs-libdispatch `INSTALL` file. Both fail with the [same errors]( https://gist.github.com/modocache/8389d5d64e39ca5a4281500f84e9ce11). Any tips? 2. I don't know much about C++, but from what I understand the C++ stdlib provides tools for asynchronous programming. I list SourceKit's uses of libdispatch in a comment on https://bugs.swift.org/browse/SR-1639. For those familiar with both C++ and libdispatch: do you think it's a good idea to migrate to C++, at least for now? Any advice would be appreciated. Thanks!! - Brian Gesiak -- Development thoughts at http://akrabat.com Daily Jotter for Mac OS X at http://dailyjotter.com ___ 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
Re: [swift-corelibs-dev] libdispatch on Linux, or C++ std::async?
The missing reference is to 'pthread_workqueue_signal_np()' which was added to libpwq via PR #10: https://github.com/mheily/libpwq/pull/10 I suspect that you don't have the libpwq submodule checked out in swift-corelibs-libdispatch. Is there any contents in swift-corelibs-libdispatch/libpwq? If not, running: git submodule init git submodule update from the swift-corelibs-libdispatch directory should fix it. Chris From: Brian Gesiak To: Chris Bailey/UK/IBM@IBMGB Cc: Rob Allen , Swift Core Libs Date: 30/05/2016 16:51 Subject:Re: [swift-corelibs-dev] libdispatch on Linux, or C++ std::async? Thanks for the quick responses! I had tried the experimental/foundation branch as well, with no luck. Here's the full output from a clean build I just attempted: https://gist.github.com/modocache/fcf0c78908b39834448c73ac3f50c110 Prior to the build I removed my entire build directory (which included both libdispatch-linux-x86_64 and swift-linux-x86_64) and removed all build artifacts from my libdispatch directory (I used `git clean -fxd` -- Make tells me there's no target `distclean`). Looking at the build failure, it appears to be the same one that was reported in https://bugs.swift.org/browse/SR-1242. The author of that report indicates that https://github.com/apple/swift-corelibs-libdispatch/pull/64 fixes the problem. My checkout includes the commits from that pull request, but the problem remains. In any case, thanks for all your help! I'll keep trying. Any and all advice would be much appreciated! - Brian Gesiak On Mon, May 30, 2016 at 10:22 AM, Chris Bailey wrote: I'd certainly recommend picking up the experimental/foundation branch as Rob recommends. Its where we've been doing some additional work to get properly built into the Swift toolchain and to open up some internal APIs needed by Foundation. Whilst I've been building Dispatch either independently or as part of a full toolchain using the buildbot_linux preset (with dispatch and install-dispatch added), I've just checked your build line and its working fine for me. It might be worth cleaning out any partial build you might have of libdispatch in your build directory, and running 'make distclean' from your libdispatch source directory. FYI, we've got some further changes to the experimental/foundation branch of libdispatch with should land in the next couple of days. This fixes some issues with the Swift overlay, and resolves a crash that we've found in the underlying libkqueue implementation. Chris From:Rob Allen via swift-corelibs-dev < swift-corelibs-dev@swift.org> To:Brian Gesiak Cc:Swift Core Libs Date:30/05/2016 08:08 Subject:Re: [swift-corelibs-dev] libdispatch on Linux, or C++ std::async? Sent by:swift-corelibs-dev-boun...@swift.org Hi, For what it's worth, I can't get the master branch to build either, but I can get the experimental/foundation branch to build. Regards, Rob On 30 May 2016, at 05:28, Brian Gesiak via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: Hello all! I'm working on https://bugs.swift.org/browse/SR-710, which involves porting SourceKit to Linux. SourceKit contains a handful of references to libdispatch symbols. I have two questions: 1. Could someone share a set of instructions to build swift-corelibs-libdispatch on Linux? I'm using Ubuntu 15.10 and have installed [the dependencies listed here]( https://lists.swift.org/pipermail/swift-corelibs-dev/Week-of-Mon-20151207/000122.html ). I have tried using both `swift/utils/build-script --libdispatch` as well as the instructions in the swift-corelibs-libdispatch `INSTALL` file. Both fail with the [same errors]( https://gist.github.com/modocache/8389d5d64e39ca5a4281500f84e9ce11). Any tips? 2. I don't know much about C++, but from what I understand the C++ stdlib provides tools for asynchronous programming. I list SourceKit's uses of libdispatch in a comment on https://bugs.swift.org/browse/SR-1639. For those familiar with both C++ and libdispatch: do you think it's a good idea to migrate to C++, at least for now? Any advice would be appreciated. Thanks!! - Brian Gesiak -- Development thoughts at http://akrabat.com Daily Jotter for Mac OS X at http://dailyjotter.com ___ 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
Re: [swift-corelibs-dev] [swift-evolution] [swift-users] WWDC Meetup
Hi David: I didn't respond via the form, but will definitely be there if I can amongst other meetings/plans - I know a few other people that are in the same position. Keep us updated and thanks for organising! Chris From: David Hart via swift-corelibs-dev To: Jacob Bandes-Storch Cc: Libs Swift Core , swift-users , Javier Soto , Shane S , swift-evolution Date: 08/06/2016 07:10 Subject:Re: [swift-corelibs-dev] [swift-evolution] [swift-users] WWDC Meetup Sent by:swift-corelibs-dev-boun...@swift.org Thanks for everybody that took the time to fill the form! There were many more responses than I expected, so dinner becomes difficult to organise. But thanks to a hand from another community member, we should have a venue confirmed soon. We are currently shooting for Tuesday evening. More details coming ASAP. On 07 Jun 2016, at 08:46, David Hart wrote: Of course, I wouldn’t want to exclude anybody by default! In that case, I’m proposing dinner somewhere. I’ve setup a Google Forms to help organise it: http://goo.gl/forms/Oq6dK9fPNSCAVfL72 On 07 Jun 2016, at 08:43, Jacob Bandes-Storch via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: +1 to both points :) On Mon, Jun 6, 2016 at 11:11 PM Javier Soto via swift-corelibs-dev < swift-corelibs-dev@swift.org> wrote: I would love to join as well!! I'd like to propose perhaps to plan something alternative to beers to keep it inclusive to members who may not be 21 or like to drink alcohol :) On Mon, Jun 6, 2016 at 3:49 PM Shane S via swift-evolution < swift-evolut...@swift.org> wrote: +1 I'd love to put some faces to some names :) sounds fun! Shane On Jun 6, 2016, at 4:56 AM, Rod Brown via swift-users < swift-us...@swift.org> wrote: I'd be interested in catching up. Was curious if there was going to be a meet up, either formal or informal. Sounds good. -Rod On 6 Jun 2016, at 5:36 PM, David Hart via swift-evolution < swift-evolut...@swift.org> wrote: I imagine that during WWDC a non-negligible proportion of the Swift Open Source contributors will be in or around San-Francisco. I’d very much like to profit from that opportunity to meet-up, get to know each other, talk Swift over some beers! Is anybody interested? If yes, any ideas for location? I can setup a Doodle once I see enough interest. Looking forward to meet you! ___ swift-evolution mailing list swift-evolut...@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution ___ swift-users mailing list swift-us...@swift.org https://lists.swift.org/mailman/listinfo/swift-users ___ swift-evolution mailing list swift-evolut...@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution -- Javier Soto ___ 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 ___ 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
Re: [swift-corelibs-dev] libdispatch/GCD for Swift 3.0 on Linux
Joe: FYI, if you want to be able to use the Swift 2.2 APIs for Dispatch, there's some instructions on how to build a toolchain with Dispatch included here: https://gist.github.com/seabaylea/cad7808615c52cfd2fc9d1debcad832f The third step uses a fork of Foundation from (based on master from a couple of weeks ago) that enables the use of Dispatch by Foundation itself, and adds NSURLSession support. If you just want to use Dispatch directly, you can ignore that step. As Dave says, we're working on adding Dispatch into the toolchain on Linux, and uplifting it to the new Swift 3.0 APIs - if you want to get involved, your definitely welcome! Chris From: David P Grove via swift-corelibs-dev To: swift-corelibs-dev@swift.org Date: 21/06/2016 14:02 Subject:Re: [swift-corelibs-dev] libdispatch/GCD for Swift 3.0 on Linux Sent by:swift-corelibs-dev-boun...@swift.org Hi Joe, TL;DR: right now the Swift 3.0 overlay for libdispatch is not available on Linux. But, a variety of activities are kicking off to get it there. There should be visible progress (and opportunities to help if you are so inclined) over the next few weeks. > > While working to convert some NSThread code over to GCD on Linux I > noticed that (to my dismay) GCD wasn't included in the Swift 3.0 > preview build, nor is it apart of the buildbot for Linux. Scouring > through the repository and mailing lists I can see where it is > possible to build, but there are no downstream instructions on how > to make a line like this: > > let queue = DispatchQueue(label: "com.app.queue") > > work with the swiftc compiler on Linux. > > A couple of questions: > > * are there any timelines that the principals of GCD with Swift 3 on > Linux can share; i.e., is the plan to have it included in time for > the Swift 3 GA release later this year? I certainly hope so; but cannot speak for official plans. > * are there any follow-up instructions past getting it built on how > to use it (or will make install DESTDIR place it in the right spots > in the Swift 3 toolchain hierarchy?) > I expect when things are done, it will be similar to how building the current Swift-2 dispatch overlay works on Linux. To build from source you use swift/utils/build-script with --libdispatch and it takes care of all the details (ie, it just works...). --dave ___ 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
Re: [swift-corelibs-dev] Query on NSLog
The Darwin overlay contains:
https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/Foundation.swift#L918
:
public func NSLog(_ format: String, _ args: CVarArg...) {
withVaList(args) { NSLogv(format, $0) }
}
So for consistency it would make sense to expose it on other platforms as
well.
Chris
From: Tony Parker via swift-corelibs-dev
To: Luke Howard
Cc: swift-corelibs-dev@swift.org
Date: 06/07/2016 00:57
Subject:Re: [swift-corelibs-dev] Query on NSLog
Sent by:swift-corelibs-dev-boun...@swift.org
Frankly, I think I just forgot to put a stub for it when we put out the
first set of APIs.
- Tony
On Jul 5, 2016, at 4:54 PM, Luke Howard wrote:
I added NSLog for NSKeyedArchiver so the output formatting would more
closely match Darwin, but I punted whether to make it public.
On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:
Hi Sai,
Out of curiosity, why NSLog instead of Swift’s print function?
- Tony
On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:
Hi All,
Currently NSLog has only one internal function NSLog() which can be
used only by Foundation classes.Can this be made available as a public API
?
Thanks & Regards,
Sai Hema,Java L3 Support
___
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
--
www.lukehoward.com
soundcloud.com/lukehoward
___
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
Re: [swift-corelibs-dev] Query on NSLog
Agreed - being consistent is key. The Foundation Reference currently
documents the Swift API for NSLogv() as:
https://developer.apple.com/library/mac/documentation/Cocoa/Reference/Foundation/Miscellaneous/Foundation_Functions/#//apple_ref/c/func/NSLogv
func NSLogv(_ format: String, _ args: CVaListPointer)
If that's still correct, then I guess that's what we should be adding
Chris
From: Luke Howard
To: Chris Bailey/UK/IBM@IBMGB
Cc: Tony Parker ,
swift-corelibs-dev@swift.org
Date: 06/07/2016 12:31
Subject:Re: [swift-corelibs-dev] Query on NSLog
OK, we should fix the function signature to make it identical then
(currently it does not take an argument list), and perhaps define NSLogv()
as well.
On 6 Jul 2016, at 8:36 PM, Chris Bailey wrote:
The Darwin overlay contains:
https://github.com/apple/swift/blob/master/stdlib/public/SDK/Foundation/Foundation.swift#L918
:
public func NSLog(_ format: String, _ args: CVarArg...) {
withVaList(args) { NSLogv(format, $0) }
}
So for consistency it would make sense to expose it on other platforms as
well.
Chris
From:Tony Parker via swift-corelibs-dev <
swift-corelibs-dev@swift.org>
To:Luke Howard
Cc:swift-corelibs-dev@swift.org
Date:06/07/2016 00:57
Subject:Re: [swift-corelibs-dev] Query on NSLog
Sent by:swift-corelibs-dev-boun...@swift.org
Frankly, I think I just forgot to put a stub for it when we put out the
first set of APIs.
- Tony
On Jul 5, 2016, at 4:54 PM, Luke Howard wrote:
I added NSLog for NSKeyedArchiver so the output formatting would more
closely match Darwin, but I punted whether to make it public.
On 6 Jul 2016, at 5:42 AM, Tony Parker via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:
Hi Sai,
Out of curiosity, why NSLog instead of Swift’s print function?
- Tony
On Jun 27, 2016, at 4:37 AM, Sai Kanduri via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:
Hi All,
Currently NSLog has only one internal function NSLog() which can be
used only by Foundation classes.Can this be made available as a public API
?
Thanks & Regards,
Sai Hema,Java L3 Support
___
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
--
www.lukehoward.com
soundcloud.com/lukehoward
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
--
www.lukehoward.com
soundcloud.com/lukehoward
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
Re: [swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs
I had a quick conversation with Daniel Dunbar on this. Adding -Xcc -fblocks as a default option to Swift PM (on Linux). The wrinkle is the availability of the blocks runtime - it would either need to become a pre-req for Swift, or needs one to be built into the package. Chris From: David P Grove via swift-corelibs-dev To: Swift corelibs dev Date: 28/07/2016 18:50 Subject:Re: [swift-corelibs-dev] Wrapping up Swift 3 for swift-corelibs Sent by:swift-corelibs-dev-boun...@swift.org Tony Parker wrote on 07/28/2016 01:41:55 PM: > > 1. Integrate swift-corelibs-dispatch into Foundation. Hi Tony, Hopefully this is on the task list already, but if it isn't we should add it before it gets to be too late to change the compiler... When compiling a Swift program on Linux that imports Dispatch (or Foundation once the integration is done), the user has to give the extra compilation flags -Xcc -fblocks to enable block support. We really need to land a change somewhere so that either (1) blocks support is always on for Linux or (2) importing Dispatch or Foundation automatically turns on blocks support. I have some time today and tomorrow that I could use to work on this if no one is handling it already, but I'm not sure how best to tackle the problem. Suggestions? --dave ___ 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
Re: [swift-corelibs-dev] Can't build corelibs-libdispatch on OS X
Hi Kevin: Unless something has changed very recently, Its not currently possible to build swift-corelibs-libdispatch on OSX - the build process works on Linux only. Chris From: Kevin Ballard via swift-corelibs-dev To: swift-corelibs-dev@swift.org Date: 02/08/2016 22:23 Subject:[swift-corelibs-dev] Can't build corelibs-libdispatch on OS X Sent by:swift-corelibs-dev-boun...@swift.org I want to port https://github.com/apple/swift/pull/3923 to swift-corelibs-libdispatch but I can't figure out how to build swift-corelibs-libdispatch on OS X. Running `sh autogen.sh` results in src/Makefile.am:9: error: Libtool library used but 'LIBTOOL' is undefined src/Makefile.am:9: The usual way to define 'LIBTOOL' is to add 'LT_INIT' src/Makefile.am:9: to 'configure.ac' and run 'aclocal' and 'autoconf' again. src/Makefile.am:9: If 'LT_INIT' is in 'configure.ac', make sure src/Makefile.am:9: its definition is in aclocal's search path. configure.ac does include LT_INIT, but I have no idea how to make sure its definition is in aclocal's search path. I get the same problem with swift/utils/build-script --libdispatch. -Kevin Ballard ___ 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
Re: [swift-corelibs-dev] libdispatch Arch Linux
Hi Ryan: The three failures: dispatch_select: dispatch_io dispatch_io_net most likely occur because you don't have a /usr/share/dict/words file, which you can get by installing something like the wamerican or wbritish backage. From: Ryan Lovelett via swift-corelibs-dev To: swift-corelibs-dev@swift.org Date: 13/08/2016 22:11 Subject:[swift-corelibs-dev] libdispatch Arch Linux Sent by:swift-corelibs-dev-boun...@swift.org (I know that this is not 100% expected to work yet. AND I'm working on an unsupported distro... but I thought I'd ask). Trying to build libdispatch on Linux (Arch Linux 4.6.4-1-ARCH). The build seems to go fine up until the tests. At this point there are 3 failing tests (see the attached test-suite.log). Two questions: 1. Can someone help me decipher that log to figure out what is going wrong? 2. It tells me to report the errors to libdispa...@macosforge.org. Is that something I really should do? [attachment "test-suite.log" deleted by Chris Bailey/UK/IBM] ___ 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
Re: [swift-corelibs-dev] f8c3fe6c breaks on Darwin
We're currently making the last few changes which should mean that
Dispatch always builds on Linux if your using Foundation, and as Dispatch
is already there on Darwin, it should mean we can remove the condition
statements entirely.
Chris
From: Luke Howard via swift-corelibs-dev
To: Tony Parker via swift-corelibs-dev
Date: 23/08/2016 08:55
Subject:Re: [swift-corelibs-dev] f8c3fe6c breaks on Darwin
Sent by:swift-corelibs-dev-boun...@swift.org
Also, the NSData test is broken on Darwin when libdispatch is enabled –
possibly the system DispatchData is being pulled in and something funny
happens, this seems to work around it but I’m not sure if it is the
correct fix:
+++ b/Foundation/NSData.swift
@@ -228,7 +228,7 @@ open class NSData : NSObject, NSCopying,
NSMutableCopying, NSSecureCoding {
}
open override func isEqual(_ value: Any?) -> Bool {
-#if DEPLOYMENT_ENABLE_LIBDISPATCH
+#if DEPLOYMENT_ENABLE_LIBDISPATCH && !os(OSX)
if let data = value as? DispatchData {
if data.count != length {
return false
On 23 Aug 2016, at 5:46 PM, Luke Howard via swift-corelibs-dev <
swift-corelibs-dev@swift.org> wrote:
Enabling libdispatch seems to break the tests on Darwin because
DEPLOYMENT_ENABLE_LIBDISPATCH is not added to the XCode project build
flags (both for the C/Swift compilers).
--
www.lukehoward.com
soundcloud.com/lukehoward
___
swift-corelibs-dev mailing list
swift-corelibs-dev@swift.org
https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
--
www.lukehoward.com
soundcloud.com/lukehoward
___
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
[swift-corelibs-dev] Server APIs Project - next steps
Since announcing the Server APIs project and work group only one week ago we seen a considerable amount of early interest. There are now over 30 people signed up in addition to the steering team, and some health discussion has started on the mailing list. One question that's been raised more than once is: Ok, there's a project page and a work group, but what happens next? The Server APIs Project pages outlined three initial focus areas: Base Networking, Security and Encryption, and HTTP and WebSockets. For each of these areas we'll be forming a sub-team whose initial task is to building a Swift Evolution "Pitch". This means collating requirements from the community around function, capability, and usage models, alongside evaluating available technologies like C libraries that could be used to help implement low level function, or existing Swift packages that ideas could be borrowed from, to form a high level sketch of the capabilities that the APIs would implement and an overview of how they would be implemented. Based on feedback from the community, the iterative process of prototyping and development can then begin. The Development Process is documented in more detail on the Server APIs Project page on Swift.org. Over the next few days we'll start to schedule kick-off meetings for each of the sub-teams. We'll be using Doodle polls to try to schedule a time that works for most participants. Obviously what ever day/time it ends up being, there will be some people that cannot make it - don't worry though, we'll be publishing the agenda (along with a request for agenda items) and a full set of minutes on GitHub. Chris___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
[swift-corelibs-dev] Server APIs: networking and security kick-off meetings
In order to try to schedule kick-off meetings for the Server APIs focus areas, I've set up Doodle polls for the networking and security kick-offs, with the aim of trying to hold those this week: Server APIs: Networking sub-team kickoff http://doodle.com/poll/b5vy7s8vs9pbcb7y Server APIs: Security sub-team kickoff http://doodle.com/poll/6xc84g5kfgv3ebv5 we'll follow up with the HTTP kick-off once we have these two scheduled. The Doodle poll lets you set what time(s) you'd be able to make a call - we'll use either Webex or Google Hangouts for the meeting, so you'll be able to use your network connection to take part. We won't be recording the call, but we will publish full agenda and minutes to GitHub afterwards. If you'd like to take part, but can't make any of the available times, fill in your name and select "Cannot make it". If there's enough people that cannot make it, we'll postpone to a later date. Chris___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
Re: [swift-corelibs-dev] [swift-server-dev] Server APIs: networking and security kick-off meetings
Based on current feedback, the schedule is looking like it will be: Security: Thursday 3rd: 6pm CET, 5pm UK, 12pm EST, 9am PST Networking Friday 4th: 6pm CET, 5pm UK, 12pm EST, 9am PST If your interested in taking part, and haven't entered a preference into the polls, please do as soon as possible. Chris From: Chris Bailey via swift-server-dev To: swift-server-...@swift.org, swift-corelibs-dev@swift.org Date: 02/11/2016 15:09 Subject:[swift-server-dev] Server APIs: networking and security kick-offmeetings Sent by:swift-server-dev-boun...@swift.org In order to try to schedule kick-off meetings for the Server APIs focus areas, I've set up Doodle polls for the networking and security kick-offs, with the aim of trying to hold those this week: Server APIs: Networking sub-team kickoff http://doodle.com/poll/b5vy7s8vs9pbcb7y Server APIs: Security sub-team kickoff http://doodle.com/poll/6xc84g5kfgv3ebv5 we'll follow up with the HTTP kick-off once we have these two scheduled. The Doodle poll lets you set what time(s) you'd be able to make a call - we'll use either Webex or Google Hangouts for the meeting, so you'll be able to use your network connection to take part. We won't be recording the call, but we will publish full agenda and minutes to GitHub afterwards. If you'd like to take part, but can't make any of the available times, fill in your name and select "Cannot make it". If there's enough people that cannot make it, we'll postpone to a later date. Chris___ swift-server-dev mailing list swift-server-...@swift.org https://lists.swift.org/mailman/listinfo/swift-server-dev ___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
[swift-corelibs-dev] Server APIs: Security kick-off meeting today at 5pm UK, 1pm EST, 10am PST
We now have a set schedule for the Security sub-team kick-off meeting for today. The meeting will be at the following time: 6pm CET 5pm UK 1pm EST 10am PST There will be a live meeting on Webex, and meeting agenda and notes taken via Google docs: WebEx: https://meetings.webex.com/collabs/#/meetings/detail?uuid=M1DFRNTQ8M1TEF4BEK1FHQ7ZL4-1T5J&rnd=425451.56230 Agenda: https://docs.google.com/document/d/1zYkQF0WR0fUiafAcgmumJRH5TLSm_MboRuxkYejTq44/edit If you'd like to add anything to the agenda ahead of time, please update the agenda document. Thanks, Chris From: Chris Bailey via swift-server-dev To: Chris Bailey Cc: swift-server-...@swift.org, swift-corelibs-dev@swift.org Date: 02/11/2016 21:59 Subject:Re: [swift-server-dev] Server APIs: networking and securitykick-offmeetings Sent by:swift-server-dev-boun...@swift.org Based on current feedback, the schedule is looking like it will be: Security:Thursday 3rd:6pm CET, 5pm UK, 12pm EST, 9am PST NetworkingFriday 4th:6pm CET, 5pm UK, 12pm EST, 9am PST If your interested in taking part, and haven't entered a preference into the polls, please do as soon as possible. Chris From:Chris Bailey via swift-server-dev To:swift-server-...@swift.org, swift-corelibs-dev@swift.org Date:02/11/2016 15:09 Subject:[swift-server-dev] Server APIs: networking and security kick-offmeetings Sent by:swift-server-dev-boun...@swift.org In order to try to schedule kick-off meetings for the Server APIs focus areas, I've set up Doodle polls for the networking and security kick-offs, with the aim of trying to hold those this week: Server APIs: Networking sub-team kickoff http://doodle.com/poll/b5vy7s8vs9pbcb7y Server APIs: Security sub-team kickoff http://doodle.com/poll/6xc84g5kfgv3ebv5 we'll follow up with the HTTP kick-off once we have these two scheduled. The Doodle poll lets you set what time(s) you'd be able to make a call - we'll use either Webex or Google Hangouts for the meeting, so you'll be able to use your network connection to take part. We won't be recording the call, but we will publish full agenda and minutes to GitHub afterwards. If you'd like to take part, but can't make any of the available times, fill in your name and select "Cannot make it". If there's enough people that cannot make it, we'll postpone to a later date. Chris___ swift-server-dev mailing list swift-server-...@swift.org https://lists.swift.org/mailman/listinfo/swift-server-dev ___ swift-server-dev mailing list swift-server-...@swift.org https://lists.swift.org/mailman/listinfo/swift-server-dev ___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
[swift-corelibs-dev] Server APIs: Networking kick-off meeting at 5pm UK, 1pm EST, 10am PST on Friday 4th
We now have a set schedule for the Networking sub-team kick-off meeting for Friday 4th Nov (ie, tomorrow). The meeting will be at the following time: 6pm CET 5pm UK 1pm EST 10am PST There will be a live meeting on Webex, and meeting agenda and notes taken via Google docs: WebEx: https://meetings.webex.com/collabs/#/meetings/detail?uuid=M2BGRS5MF22PQOJZZK1L8D2A9S-1T5J&rnd=400574.57602 Agenda: https://docs.google.com/document/d/14MEE8erSa9sOyD62eSHhwppInUAu5x2AE7-1divd5G0/edit?usp=sharing If you'd like to add anything to the agenda ahead of time, please update the agenda document. Thanks, Chris ___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
Re: [swift-corelibs-dev] [swift-server-dev] Server APIs: Networking kick-off meeting at 5pm UK, 1pm EST, 10am PST on Friday 4th
Hi Tyler: There's a number of people out this coming week because of the Swift Summit etc, so the next one is likely to be the week after at the earliest. I'll try to get another Doodle poll out in the next couple of days. This time they'll be options over a number of days, and a bit more time to organise ourselves, so hopefully everyone that's interested will be able to make it. Chris From: Tyler Cloutier To: Chris Bailey/UK/IBM@IBMGB Cc: swift-server-...@swift.org, swift-corelibs-dev@swift.org Date: 06/11/2016 19:40 Subject:Re: [swift-server-dev] Server APIs: Networking kick-off meeting at 5pm UK, 1pm EST, 10am PST on Friday 4th I was unable to make this meeting. Is there a planned next meeting? I don’t see anything in the agenda document. Tyler On Nov 3, 2016, at 1:27 PM, Chris Bailey via swift-server-dev < swift-server-...@swift.org> wrote: We now have a set schedule for the Networking sub-team kick-off meeting for Friday 4th Nov (ie, tomorrow). The meeting will be at the following time: 6pm CET 5pm UK 1pm EST 10am PST There will be a live meeting on Webex, and meeting agenda and notes taken via Google docs: WebEx: https://meetings.webex.com/collabs/#/meetings/detail?uuid=M2BGRS5MF22PQOJZZK1L8D2A9S-1T5J&rnd=400574.57602 Agenda: https://docs.google.com/document/d/14MEE8erSa9sOyD62eSHhwppInUAu5x2AE7-1divd5G0/edit?usp=sharing If you'd like to add anything to the agenda ahead of time, please update the agenda document. Thanks, Chris ___ swift-server-dev mailing list swift-server-...@swift.org https://lists.swift.org/mailman/listinfo/swift-server-dev ___ swift-corelibs-dev mailing list swift-corelibs-dev@swift.org https://lists.swift.org/mailman/listinfo/swift-corelibs-dev
