Re: [CFV] how to mark protected items?

Hans Lellelid wrote:

Daniel Convissor wrote:

Not in PHP 4. But when this poor shmoe upgrades to PHP 5, they're screwed.

They're screwed anwyay, Dan. Any PEAR package that is gonna upgrade to PHP5 is going to do so to take advantage of new language features. There is no easy migration path for user schmoe when all of a sudden the underlying package starts throwing PEAR_Exception instead of returning PEAR_Error.

This doesn't have to be true, but it's not what this thread is about. See the thread I'll start in a minute for more discussion.

IMHO upgradeablity should not be a consideration when designing coding standards that will apply to PHP5. PHP5 is an entirely different ballgame; the OO stuff is not at all backwards compatible, even if that's what Zend would like you to believe.

I very much disagree. Code in PHP4 should have an easy upgrade path to PHP5. Consider all of the code written in PHP4. If it has to be rewritten for PHP5, PHP5 adoption is going to take a LONG time.

That said it's a great opportunity to end non-applicable practices inherited from PHP4. I'd say the '_' on protected methods/properties (if it gains the needed votes) would be one of those ideas, a product of the limitations in PHP4. Hans

-- paperCrane <Justin Patrin>