Re: [CFV] how to mark protected items?
| From: | David Costa | Date: | Tue, 22 Jun 2004 20:36:33 +0000 |
| Subject: | Re: [CFV] how to mark protected items? | ||
| References: | 1 2 3 4 5 6 7 8 9 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-31118@lists.php.net to get a copy of this message | ||
On Jun 22, 2004, at 10:32 PM, Justin Patrin wrote:
snip
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.Well, once again depends on the error level. On E_STRICT nothing will work, otherwise all will work out of the box unless you have a reassignment of $this or worst. I appreciate you disagree but this is PHP 5, is not something we can change I think. Cheers David CostaIMHO 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> -- PEAR Development Mailing List (http://pear.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php