<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div>I have to agree with Charlie Monroe that while this is doable, it's clear this is a workaround to a problem, not a viable long term language solution.</div><div><br>- Rod</div><div><br><div><br><br>Sent from my iPhone</div>On 30 May 2016, at 2:49 PM, Callionica (Swift) <<a href="mailto:swift-callionica@callionica.com">swift-callionica@callionica.com</a>> wrote:<br><br></div><blockquote type="cite"><div><div dir="ltr">I've written up how to provide protected access control for Swift code today here:<div><br></div><div><a href="http://www.callionica.com/developer/#swift-protected">http://www.callionica.com/developer/#swift-protected</a></div><div><br><div>No compiler changes necessary for this technique and it distinguishes between methods that can only be overridden and methods that can be both called and overridden.</div></div></div>
</div></blockquote></body></html>