note 68101 added to language.oop5.visibility

This refers to previous notes on protected members being manipulated externally: It is obvious that if you were to allow methods the option of replacing protected variables with external ones it will be possible, but there is no reason not to simply use a protected method to define these, or not to write the code to allow it. Just because it is possible doesn't mean it's a problem, it simply does not allow you to be lax on the security of the class. ---- Server IP: 66.163.161.117 Probable Submitter: 82.1.217.193 (proxied: 1.1 DUBLIN_PROXY) ---- X-Spam-Status: No, hits=3.1 required=5.0 tests=DATE_MISSING,FROM_NO_LOWER autolearn=no version=2.64 ---- Manual Page -- http://www.php.net/manual/en/language.oop5.visibility.php Edit -- http://master.php.net/note/edit/68101 Del: integrated -- http://master.php.net/note/delete/68101/integrated Del: useless -- http://master.php.net/note/delete/68101/useless Del: bad code -- http://master.php.net/note/delete/68101/bad+code Del: spam -- http://master.php.net/note/delete/68101/spam Del: non-english -- http://master.php.net/note/delete/68101/non-english Del: in docs -- http://master.php.net/note/delete/68101/in+docs Del: other reasons-- http://master.php.net/note/delete/68101 Reject -- http://master.php.net/note/reject/68101 Search -- http://master.php.net/manage/user-notes.php