<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 am not sure if I should tag this subject with [pitch]? ) </div><div class=""><br class=""></div><div class="">Please don’t worry , I am not attempting to start a new</div><div class="">and infinite thread about whether or not the way scope</div><div class="">is handled in Swift is imho correct or not.</div><div class="">Errhm well, apart from that “protected” is missing,</div><div class="">but please let us not start again.. :o) </div><div class=""><br class=""></div><div class="">No, it is more or less a convenience solution to</div><div class="">prevent unnecessary wear and tear to the following keys</div><div class="">on my keyboard: [ A,E, I, P, R, T, V]</div><div class=""><br class=""></div><div class="">I prefer it, not to expose those class or struct members</div><div class="">which should not be accessible outside the class or struct</div><div class=""><br class=""></div><div class="">Currently, to prevent access to private Items,</div><div class="">I have to type the word “private” too many times:</div><div class=""><br class=""></div><div class=""><div class="">class House</div><div class="">{</div><div class=""> private var rooms = 5</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>private var roofTiles = 11201</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>private let paint = UIColor.Blue;</div><div class=""> private var yearTax: Money = “323,56"</div><div class=""> private let garageVolume = 60.0</div><div class=""><br class=""></div><div class=""> init(..) {.. }</div><div class=""><br class=""></div><div class=""> private func calculateTax() {...}</div><div class=""><br class=""></div><div class=""> public func roomsUnoccupied() -> Int {…}</div><div class=""><br class=""></div><div class=""> func roofData(……) {…}</div><div class=""><br class=""></div><div class=""> private func a{…} </div><div class="">}</div><div class=""><br class=""></div><div class="">To set the scope of a list of members I suggest the</div><div class="">“in-line scope modifiers” (anyone with a better name for it?) </div><div class=""><br class=""></div><div class="">For example if one has a source line containing the word</div><div class="">“private:” then all the following member declarations will</div><div class="">be “private” until another inline scope modifier is encountered</div><div class="">with one “default scope” to escape from it. like in the following example”</div><div class=""><br class=""></div><div class="">The compiler can detect that it is an inline scope modifier, because it ends with a colon</div><div class=""><br class=""></div><div class="">“Normal” scope modifiers, that is the ones which precede the member’s name </div><div class="">directly should imho not be allowed within such a scope block.</div><div class="">unless they would override for that specific item, but that looks ugly. </div><div class=""><br class=""></div><div class="">getter & setters and init should appear in default scope</div><div class="">(or with no in-line scope modifiers)</div><div class=""><br class=""></div><div class="">Inline scope modifiers can be specified as often as</div><div class="">desired and in arbitrary sequence. </div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><div class="">class House</div><div class="">{</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span> init(..) {.. } </div><div class=""> private: // <—— In-line scope modifier all following declarations are private here.</div><div class=""> var rooms = 5</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span> var roofTiles = 11201</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span> let paint = UIColor.Blue;</div><div class=""> var yearTax: Money = “323,56"</div><div class=""> func calculateTax() {…}</div><div class=""><div class=""> func a{…} </div></div><div class=""><br class=""></div><div class=""> public: // <—— In-line scope modifier</div><div class=""> var garageVolume = 60.0 </div><div class=""> func roomsUnoccupied() -> Int {…}</div><div class=""><div class=""> func roofData(……) {…}</div></div><div class=""><br class=""></div><div class=""> defaultscope: // <—— Return to default scope (only needed when preceding inline scope modifiers are present. )</div><div class=""><div class=""> </div></div><div class=""> func sellHouse(buyer: CustomerID) </div><div class="">}</div><div class=""><br class=""></div><div class="">See? looks a lot better, don’t you think so? </div><div class=""><div class="">it also makes sources more readable because one can </div><div class="">now conveniently group items.</div></div><div class=""><br class=""></div><div class="">100% source compatible with whatever scope </div><div class="">mechanism now or in the future is or will be deployed.</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">(The idea is not exactly new, a similar construct is available in Object Pascal.) </div><div class=""><br class=""></div><div class="">?</div><div class=""><br class=""></div><div class="">Kind Regards</div><div class="">TedvG</div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div></div></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""><br class=""></div><div class=""> </div></body></html>