Re: RfC: rethink OO inheritance strictness

This is where PHP's strengths can be seen as a weakness. If parameter overloading is wanted then it would be easier if PHP was not a loosely typed language. But, just for arguments sake, if E_STRICT was active _and_ type hinting was available for ALL types, then at compile time, you COULD build the appropriate parameter signature. And parameter overloading could work. No E_STRICT and you don't have it. E_STRICT may be the name to use as this would be breaking the "contract" between parent and child and the issue of "instance of" does appear again. I would LOVE type hinting, just so that auto documentors can say that this function requires a datetime as an integer and not a datetime as a string (sort of thing). On 02/08/06, Hartmut Holzgraefe <hartmut@mysql.com> wrote:

Ron Korving wrote: So, my suggestion is this: why not support function overloading in PHP6, because in PHPs dynamicly typed world this would require runtime checks *on every single function call* as things can't be resolved at compile time? --

Hartmut Holzgraefe, Senior Support Engineer                            .

MySQL AB, www.mysql.com -- 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&amp;r=213474731 "Standing on the shoulders of some very clever giants!"