Re: RfC: rethink OO inheritance strictness
| From: | Hartmut Holzgraefe | Date: | Wed, 02 Aug 2006 12:56:36 +0000 |
| Subject: | Re: RfC: rethink OO inheritance strictness | ||
| References: | 1 2 3 4 5 6 7 8 9 10 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-25120@lists.php.net to get a copy of this message | ||
Richard Quadling wrote:
That was done before, so it could be done again. In principle, there is nothing wrong with refactoring or even rewriting, except time and effort.totally changing the underlying type concept in an incompatible way is not refactoring, and even as a rewrite i'm strongly in doubt whether the result deserves to go by the same name as the original
We have OOP developers wanting OOP things that they've seen working fine in other languages and non-OOP'ers wondering why!Is function overloading really "an OOP thing"?
As this is a discussion forum, all things SHOULD be considered!There is a difference between discussion and brainstorming ... -- Hartmut Holzgraefe, Senior Support Engineer . MySQL AB, www.mysql.com