I see it as catch up to OOP. I've never used Java. I've used Delphi though.
I suppose the main issue is that userland sees OOP and expects things to be similar to other OOPs they've used. They're blinkered as to why it ISN'T the same! Like discrete setters/getters providing accesssibilty or being able to promote/demote visibility via inheritence. On 21/07/06, Lukas Smith <[EMAIL PROTECTED]> wrote:
Derick Rethans wrote: > On Fri, 21 Jul 2006, Lukas Smith wrote: > >> Richard Quadling wrote: >>> I agree with this point. The sub class is a valid entity in its own >>> right. The methods (and the parameters) it has are part of that class. >>> If they overwrite a parent class's method, then fine. Instance of >>> either class would have different parameters for the same named >>> method. >> Its not about being "right". Acedemically Marcus changes are correct. The >> question is just if we want to force this way of working onto PHP, or if it >> makes more sense to make it optional. > > I would say that if you want to use it in the "wrong" lenient way that > you need to mark your classes as such and not the other way around. This > might also have the effect that people see PHP as a better language > (because of the OO stuff is "correct" by default. Or it will mean that the established user base gets ticked off and the other people see PHP as just playing catch up to Java. Now is probably the time to hire a consulting firm ;) regards, Lukas -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
-- ----- Richard Quadling Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731 "Standing on the shoulders of some very clever giants!" -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
