<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="">One bonus it is a real word so autocorrect doesn’t fix it! I checked the dictionary and there are no negative or misleading meaning. <div class=""><br class=""></div><div class="">It is a verb though, this is not being used as a verb in this case. </div><div class=""><br class=""></div><div class=""><a href="http://www.dictionary.com/browse/interfile" class="">http://www.dictionary.com/browse/interfile</a></div><div class=""><div class=""><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Mar 30, 2016, at 10:04 PM, Paul Ossenbruggen <<a href="mailto:possen@gmail.com" class="">possen@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">public<br class="">internal<br class="">interfile<br class="">private<br class=""><br class="">still googleable and very clear its scope and meaning, nice latin root. Doesn’t overload “private”, slightly shorter. <br class=""><br class=""><br class=""><blockquote type="cite" class="">On Mar 30, 2016, at 9:46 PM, Thorsten Seitz via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class="">Looks good to me.<br class=""><br class="">-Thorsten <br class=""><br class=""><blockquote type="cite" class="">Am 31.03.2016 um 06:22 schrieb Chris Lattner via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>>:<br class=""><br class=""><blockquote type="cite" class="">On Mar 23, 2016, at 10:13 PM, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</a>> wrote:<br class="">How about we continue this trend, and follow other existing Swift keywords that merge two lowercase words (associatedtype, typealias, etc), and use:<br class=""><br class=""> public<br class=""> moduleprivate<br class=""> fileprivate<br class=""> private<br class=""><br class="">The advantages, as I see them are:<br class="">1) We keep public and private meaning the “right” and “obvious” things.<br class="">2) The declmodifiers “read” correctly.<br class="">3) The unusual ones (moduleprivate and fileprivate) don’t use the awkward parenthesized keyword approach.<br class="">4) The unusual ones would be “googable”.<br class="">5) Support for named submodules could be “dropped in” by putting the submodule name/path in parens: private(foo.bar.baz) or moduleprivate(foo.bar). Putting an identifier in the parens is much more natural than putting keywords in parens.<br class=""></blockquote><br class="">I’ve seen a number of concerns on this list about moduleprivate, and how it penalizes folks who want to explicitly write their access control. I’ve come to think that there is yes-another possible path forward here (which I haven’t seen mentioned so far):<br class=""><br class="">public<br class="">internal<br class="">fileprivate<br class="">private<br class=""><br class="">The advantages, as I see them are:<br class="">1) We keep public and private meaning the “right” and “obvious” things.<br class="">2) The declmodifiers “read” correctly.<br class="">3) Compared to Swift 2, there is almost no change. The only thing that changes is that some uses of Swift 2 “private” will be migrated to “fileprivate”, which makes the intent of the code much more clear.<br class="">4) fileprivate is the unusual and not-really-precedented-in-other-languages modifier, and it would still be “googable”.<br class="">5) The addresses the “excessively long” declmodifier problem that several people are concerned with.<br class="">6) Support for named submodules could be “dropped in” by parameterizing “internal”.<br class=""><br class="">Thoughts?<br class=""><br class="">-Chris<br class="">_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></blockquote>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></blockquote><br class=""></div></div></blockquote></div><br class=""></div></div></div></body></html>