Re: Private Methods
Re: Private Methods
- Subject: Re: Private Methods
- From: Quincey Morris <email@hidden>
- Date: Tue, 18 Aug 2015 22:19:39 +0000
On Aug 18, 2015, at 14:50 , Charles Srstka <email@hidden> wrote:
>
> Look a little closer, and you’ll notice that the app code was in Swift (like your app would be), and the framework code was in Objective-C (like the Foundation/AppKit classes are).
Actually, I did look, but obviously I did not see.
But, in my own defense, I was looking for verification first that the mechanism is safe in 100% pure Swift. The next thing to verify is whether it’s safe with an @objc base class in Swift. Only if both those things are safe does it make any sense to wonder if an Obj-C base class is safe.
However, the test you did doesn’t give much cause for optimism. I suppose *selectors* would have to be namespaced to solve the problem for the Obj-C runtime, wouldn’t it? For compatibility reasons, that seems unlikely, which makes it unlikely that this problem will ever be solved for Cocoa frameworks.
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden