Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24813
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44C09F31.9090505@php.net>
Date: Fri, 21 Jul 2006 11:32:33 +0200
User-Agent: Thunderbird 1.5.0.4 (Windows/20060516)
MIME-Version: 1.0
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
References: <EB.71.29121.B6690C44@pb1.pair.com> <10845a340607210208l2ffea986ndd77a0a0c50a9965@mail.gmail.com> <44C09BE2.7000201@php.net> <Pine.LNX.4.62.0607211127570.5096@localhost>
In-Reply-To: <Pine.LNX.4.62.0607211127570.5096@localhost>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness
From: lsmith@php.net (Lukas Smith)

Derick Rethans wrote:
> On Fri, 21 Jul 2006, Lukas Smith wrote:
> 
>> Richard Quadling wrote:
>>> I agree with this point. The sub class is a valid entity in its own
>>> right. The methods (and the parameters) it has are part of that class.
>>> If they overwrite a parent class's method, then fine.  Instance of
>>> either class would have different parameters for the same named
>>> method.
>> Its not about being "right". Acedemically Marcus changes are correct. The
>> question is just if we want to force this way of working onto PHP, or if it
>> makes more sense to make it optional.
> 
> I would say that if you want to use it in the "wrong" lenient way that 
> you need to mark your classes as such and not the other way around. This 
> might also have the effect that people see PHP as a better language 
> (because of the OO stuff is "correct" by default.

Or it will mean that the established user base gets ticked off and the 
other people see PHP as just playing catch up to Java. Now is probably 
the time to hire a consulting firm ;)

regards,
Lukas