<div dir="ltr">I am sure that fileprivate is very useful. SE-0025 did not ask to remove it.</div><br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 25, 2016 at 8:57 PM Ilya Belenkiy <<a href="mailto:ilya.belenkiy@gmail.com">ilya.belenkiy@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">all of these names (public, internal, private, local) have specific meaning in the context of computer languages. I think that we should use standard terms and give them the expected meaning. I did not do this originally with SE-0025 and suggested "scoped" because I thought that "private" could not be changed. But since it can, we should definitely use it, and give it the meaning that most people expect.</div><div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Fri, Mar 25, 2016 at 7:57 PM Brent Royal-Gordon via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> I honestly still think "public, internal, private, local" is a better taxonomy.. It's true that "internal" and "private" aren't automatically ordered relative to each other (and maybe not even "local"), but they're all adjectives (unlike "module" and "file"), and they're not awkward to read or to use in conversation. But both the core team and the list disagree, mainly because (a) it aligns 'private' more closely with other languages, and (b) if you're not thinking about it, more restrictive is better than less. (Both of which I agree are good ideas.)<br>
<br>
If we're not married to "private" being the most private access level, I think there is a word that implies more privacy than "private": "secret". Something that's private is often still shared with trusted people, but something that's secret is very carefully protected indeed. "Three may keep a secret, if two of them are dead."<br>
<br>
So then our four access levels would be:<br>
<br>
* public<br>
* internal<br>
* private<br>
* secret<br>
<br>
--<br>
Brent Royal-Gordon<br>
Architechies<br>
<br>
_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
</blockquote></div></div></blockquote></div>