<div dir="ltr"><p style="margin:0px;font-size:13px;line-height:normal;font-family:'Helvetica Neue'">Maybe it's good thing that we just discussed it. After replying to Matthew, this meaning private feels so wrong that I will update <span style="color:#000000"> </span>the proposal to disallow this. Private should mean private.</p><div><div><br><div class="gmail_quote"><div dir="ltr">On Mon, Mar 28, 2016 at 7:27 AM Brent Royal-Gordon <<a href="mailto:brent@architechies.com">brent@architechies.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> We already had a very long discussion about all of these topics.<br>
<br>
I am not suggesting you change the design. I am suggesting you clarify the description of your existing design so that everyone understands what it means, because confusion is rampant.<br>
<br>
> I'd like to keep "private" to be completely private and not allow class injection to gain access, but this is an edge case that could be argued either way. I can definitely live with a pure scoped access for consistency and don't want to argue the edge case in a never ending discussion.<br>
<br>
<br>
So what you're saying is, you are purposefully writing the proposal vaguely so that everyone can assume it says whatever they imagine it says, and thus more people will support the proposal?<br>
<br>
This is no way to design a programming language.<br>
<br>
--<br>
Brent Royal-Gordon<br>
Architechies<br>
<br>
</blockquote></div></div></div></div>