Re: Calling parent's constructor
| From: | Zeev Suraski | Date: | Thu, 14 Dec 2000 13:04:05 +0000 |
| Subject: | Re: Calling parent's constructor | ||
| References: | 1 2 3 4 | Groups: | php.dev |
| Request: | Send a blank email to php-dev+get-41346@lists.php.net to get a copy of this message | ||
At 10:14 14/12/2000, Kristian Köhntopp wrote:
Zeev Suraski wrote:Christ. I *love* it when you state opinions as axioms. But let's agree to disagree.No, probably not. My original suggestion was to recognize parent::parent() construct -- I don't know how Zeev & Andi would react to that.Seriously, I think it makes sense. Calling the parent constructor is basic functionality and should be easy to do. Hell, it's even easy to implement. Inherited constructors are already broken in Zend, and cannot be fixed any more.
This looks sensible. I suggest parent::__parent(), though, to go along with __wakeup(), __sleep(), and __delegate().At the risk of giving a few people heart attacks from surprise, I'll agree with you here. That's the solution I thought about for this issue as well. Zeev -- Zeev Suraski <zeev@zend.com> CTO, Zend Technologies Ltd. http://www.zend.com/