[PEPr] +1 for RFC::ProtectedMembers
| From: | PEPr | Date: | Sat, 03 Jul 2004 18:45:52 +0000 |
| Subject: | [PEPr] +1 for RFC::ProtectedMembers | ||
| Groups: | php.pear.dev | ||
| Request: | Send a blank email to pear-dev+get-31533@lists.php.net to get a copy of this message | ||
Heino H. Gehlsen (http://pear.php.net/user/heino) has voted +1 on the proposal for
RFC::ProtectedMembers.
Proposal information:
http://pear.php.net/pepr/pepr-proposal-show.php?id=99
Vote information:
http://pear.php.net/pepr/pepr-vote-show.php?id=99&handle=heino
This vote is conditional. The condition is:
Underscore prefixing should still be allowed when it serve an actual purpose (e.g. hiding
methods that have to be accessible due to internal complexity), but it should not be required common
practice since protected methods (and variables) should be named as if they were public, which they
might become later on (unless they are final).
Renaming of protected methods (and variables) prefixed with an underscore should be considered a BC
issue (they are as much part of the API as the public stuff)! As should (perhaps) renaming of
private variables due to possible implementations of __sleep() in inheriting classes...
--
Sent by PEPr, the automatic proposal system at http://pear.php.net