Re: Re: [PEPr] Comment on RFC::ProtectedMembers

Lukas Smith wrote:

For the record: I think this is a non issue. I find the underscore to be convinient, little effort to do, and not such a dramatic uglifier of my code. Then again while I am debugging my code locally in php5 I will be able to quickly make out if I screwed up. if this is going to help me while doing emergency repairs on a remote host is another question ..?

It may be trivial, but if so then it should be a recommendation not a requirement. You do it, that's fine; it may make your code more convenient to read, but it won't make mine anything but uglier. I do agree it's trivial, but I just don't want my code constrained by a non-sensical, trivial, requirement that is unique to PHP -- nay, PEAR -- and which was voted into existence by people who don't use PHP5. So, would PHPUnit2 be forced to break BC and prefix all protected members with '_'? Hans