<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-wrap;" class="">Well, anyways, with Swift 3 it no longer is as simple as it is in Obj-C. New modifiers were introduced by request. I feel it's good and means everybody agrees Obj-C modifiers aren't sufficient for Swift.</div></div></blockquote><div>Well… no ;-)</div><div>I'm not sure if there is a single thing in the universe where really everybody agrees on — right now, there is nothing more than a small group that has a vague agreement that there is room for improvement with the current access levels; most Swift users aren't even aware of this discussion at all (and most likely never will be ;-)</div>[In situations like this, I really dislike the restrictions of this medium… with something like a Wiki, it would be much easier to set up a table so that we could at least collect the opinions from the people discussing now.]</div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-wrap;" class="">What I mean, initial arguments should apply no more and I hope Apple will not be too rigid with current status.<br class=""></div></div></blockquote><div>I agree on the latter — but it might be the case that fundamental changes to Swift won't be considered anymore</div><br class=""><blockquote type="cite" class=""><div class=""><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; white-space: pre-wrap;" class="">What I mean, though, the new introductions of access modifiers feel quite some "patchy".<br class=""></div></div></blockquote><div>Yes… but imho your suggestion which adds additional levels makes it even more patchy:</div><div>"protected" might be familiar to some developers, but "inner" is just a new magic word tacked onto the language.</div><div>For me, this is actually the worst direction to take: Adding more and more new modifiers instead of really rethinking the topic from scratch.</div><div><br class=""></div><div><br class=""></div></div></body></html>