Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24805
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44C098AB.8020509@php.net>
Date: Fri, 21 Jul 2006 11:04:43 +0200
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Michael Wallner <mike@php.net>
Cc: internals@lists.php.net
References: <EB.71.29121.B6690C44@pb1.pair.com>
In-Reply-To: <EB.71.29121.B6690C44@pb1.pair.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: RfC: rethink OO inheritance strictness
From: lsmith@php.net (Lukas Smith)

Michael Wallner wrote:
> 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.

Aternatively there has been the idea of a flag to mark classes that are 
to follow stricter rules.

regards,
Lukas