This was never really addressed before in coding standards. That said,
it was up to the individual develpers to properly identify when to use
private.
In general, there are in my mind very few instances or compelling
reasons to use the private visibility in framework code. Since
extensibility or "extend everything" is more of the perspective/motto of
the framework, protected should be the visibility developers use by default.
File a ticket. It will be addressed in version 2.0 (we can consider
changing visibility in 1.11 if there are no serious BC concerns).
-ralph
Jason Webster wrote:
Before I file a ticket, I just wanted to check:
Is there any rational reason behind the $_db, $_table, and $_columnMap
properties of Zend_Log_Writer_Db being marked as private rather than
protected?
It makes subclassing it basically useless/impossible, and subsequently
creates a copy and paste code maintenance nightmare.
