Hello Stephane, your right with comparing development time to computer performance (total cost of ownership model). So feel free to remember me as soon as we start developing php 5.1. Maybe we can add somthing that lets you call non present magical methods (__construct/__destruct/__clone) even if they are not present without a huge waste of time in execution.
marcus Friday, January 23, 2004, 11:53:02 AM, you wrote: > Marcus, > The idea behind this kind of request is to speed up development time. > And the way a language and its base classes are implemented could really > help to reach this goal. > When you write "a change is a change", you're right. But the way you > have written your code could really reduce the risk of bugs. And > systematically calling parent::... is one of it. > I also understand when you consider as a non sense calling an empty > method which slows down execution for nothing. > Except that personally I really favour develop time rather than > execution speed. Upgrading a computer is less expensive than spending > hours to fix bugs. > Implementing a common base class with empty methods (or Chris' > proposal, just do not report error) does not impact performance (just > don't call them), but allows people having a different view on programming > to do it. > Finally my request to implement it within PHP would limit the number of > class trees, all world wide classes would have the same base class. Nice > OOP vision, isn't it ;-) > Regards, > Stephane -- Best regards, Marcus mailto:[EMAIL PROTECTED] -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
