Re: Re: [PEPr] Comment on RFC::ProtectedMembers
| From: | Aidan Lister | Date: | Mon, 28 Jun 2004 10:36:45 +0000 |
| Subject: | Re: Re: [PEPr] Comment on RFC::ProtectedMembers | ||
| References: | 1 2 3 4 5 6 7 8 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-31273@lists.php.net to get a copy of this message | ||
> for b) - I guess it's up to the programmer to decide. - If you decide to
> make something protected, you are enforcing a usage requirement. In the
> authors view should it be allowable for an extended class to decrease
> the protection? - Yes: = use public syntax, No: = use private syntax.
But then you have some code with prefixes and some without and the
developer/user have no idea what they mean. If you want to make prefixing up
to the author, then make prefixing private vars optional as well.