doctrine/dbal — pull request #70 by damz (2011-11-01 18:33:05+00:00)
Title: Replace all the 'private' by 'protected' visibility modifiers

Hi there!

I have started some preliminary work to move the Drupal project to Doctrine DBAL. We already have a heavy (custom) DBAL based on PDO, and we have the need to sub-class a few classes (especially \DBAL\Statement) that contain private modifiers.

Any reason not to make those protected? There is not a ton of reasons to use private in PHP, other then on final classes.

Damien