<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 class="">I like :</div><div class=""><br class=""></div><div class="">- public</div><div class="">- modulewide or moduleprivate or internal</div><div class="">- filewide or fileprivate</div><div class="">- private</div><div class=""><br class=""></div><div class="">I really dislike interfile because the word exists and means something else</div><div class="">I dislike intermodule, inmodule and infile because I don't find them intuitive at all.</div><div class=""><br class=""></div><div class="">I prefer the -wide flavors because they're shorter than the -private flavors, and because -wide is an existing suffix in english.</div><div class="">Internal has the advantage of no modification but if we want to change it, now is the time.</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">Le 31 mars 2016 à 11:10, Ross O'Brien via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> a écrit :</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class=""><span style="font-size:13px" class="">> public</span><br style="font-size:13px" class=""><span style="font-size:13px" class="">> internal</span><br style="font-size:13px" class=""><span style="font-size:13px" class="">> interfile</span><br style="font-size:13px" class=""><span style="font-size:13px" class="">> private</span><br style="font-size:13px" class=""></div><div class=""><br class=""></div>Linguistically, I really like this direction. 'interfile' is one word, it reads as an adjective, it can be used in conversation (this has interfile visibility), and it's clear about where its visibility ends.<div class=""><br class=""></div><div class="">It just doesn't mean what you think it means.</div><div class=""><br class=""></div><div class="">'inter' means 'between'. See: 'intergalactic', 'interstellar', 'international', 'internet'. So 'interfile' would have to mean 'visible between files' - i.e. an interfile symbol in one file is visible in another file. The prefix you're looking for, meaning 'internal', is 'intra' (see: 'intravenous', 'intranet').</div><div class=""><br class=""></div><div class="">So the scale would become:</div><div class=""><br class=""></div><div class="">public / intermodule</div><div class="">internal / intramodule / interfile</div><div class="">intrafile</div><div class="">private</div><div class=""><div class=""><br class=""></div></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Thu, Mar 31, 2016 at 6:04 AM, Paul Ossenbruggen via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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="">
<div class="HOEnZb"><div class="h5"><br class="">
<br 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="">
>> 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="">
>>> 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="">
>><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="">
>> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><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="">
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
<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="">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="">
</div></div></blockquote></div><br class=""></div>
_______________________________________________<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=""></div></blockquote></div><br class=""></div></body></html>