Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24821
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Reply-To: <Jared.Williams1@ntlworld.com>
To: "'Michael Wallner'" <mike@php.net>,
	<internals@lists.php.net>
Date: Fri, 21 Jul 2006 12:20:00 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
In-Reply-To: <EB.71.29121.B6690C44@pb1.pair.com>
Thread-Index: Acaso2+use9Nf0nIRACw3koZYGmzvQAE7uAg
Message-ID: <20060721111908.KGAB644.aamtaout01-winn.ispmail.ntl.com@win2ks>
Subject: RE: [PHP-DEV] RfC: rethink OO inheritance strictness
From: jared.williams1@ntlworld.com ("Jared Williams")
References: <EB.71.29121.B6690C44@pb1.pair.com>


> Hi (Marcus),
> 
> unfortunately I'm not very happy with the direction OO 
> strictness takes
> in PHP.  I'm sure I'm not alone and many people second this feeling.
> 
> 
> Precisely, let's have a look at the following:
> 
> mike@honeybadger:~/build/php-5.2-debug$ cli 
> -d"error_reporting=8191" -r 'class c{function f(){}} class d 
> extends c{function f($a){}}'
> Strict Standards: Declaration of d::f() should be compatible 
> with that of c::f() in Command line code on line 1
> 
> mike@honeybadger:~/build/php-unicode-debug$ cli 
> -d"error_reporting=8191" -r 'class c{function f(){}} class d 
> extends c{function f($a){}}'
> Fatal error: Declaration of d::f() must be compatible with 
> that of c::f() in Command line code on line 1
> 
> 
> I *really* think that this enforcements are no good idea and
> I _beg_ you that we leave this "area" to interfaces.
> 

Not sure why this is necessary, why doesn't

Class C 
{
     function f() { } 
}

Class D 
{
     private $c;
     function __construct(C $c) { $this->c = $c; }
     function f($a) { }
}

work, with PHP's duck typing?

Jared