hi, My two cents:
For one I do think that enforcing strictness, or as I see it, clean code and implementation, should be done in php. We did not do that in the past and it has created more issues than anything else in the long run. One solution to solve the need of having different methods or constructors signatures is to support multiple signature per method or constructor, as long as the signature of the parent class or interface is available. This is something becoming more and more common in other languages and is actually very handy. Having such things would have also avoided bad (per design while necessary) sutff like the recent reflection function to create objects without invoking the constructor. On Sat, Sep 17, 2011 at 11:39 PM, Richard Quadling <rquadl...@gmail.com> wrote: > A subclass can completely divorce itself from the superclass. > > But not with an interface. > > > PHP has always been a very very flexible language. Cheers, -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org -- PHP Internals - PHP Runtime Development Mailing List To unsubscribe, visit: http://www.php.net/unsub.php
