Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:24811
Return-Path: <derick@php.net>
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Delivered-To: mailing list internals@lists.php.net
Received: (qmail 31337 invoked by uid 1010); 21 Jul 2006 09:30:50 -0000
Delivered-To: ezmlm-scan-internals@lists.php.net
Delivered-To: ezmlm-internals@lists.php.net
Received: (qmail 31321 invoked from network); 21 Jul 2006 09:30:50 -0000
Received: from unknown (HELO lists.php.net) (127.0.0.1)
  by localhost with SMTP; 21 Jul 2006 09:30:50 -0000
X-PHP-List-Original-Sender: derick@php.net
X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4)
Received: from ([82.94.239.5:34536] helo=jdi.jdi-ict.nl)
	by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP
	id 0C/04-29121-9CE90C44 for <internals@lists.php.net>; Fri, 21 Jul 2006 05:30:50 -0400
Received: from localhost (localhost [127.0.0.1])
	by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k6L9Ukqs015228;
	Fri, 21 Jul 2006 11:30:46 +0200
Date: Fri, 21 Jul 2006 11:29:07 +0200 (CEST)
X-X-Sender: derick@localhost
To: Lukas Smith <lsmith@php.net>
cc: PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <44C09BE2.7000201@php.net>
Message-ID: <Pine.LNX.4.62.0607211127570.5096@localhost>
References: <EB.71.29121.B6690C44@pb1.pair.com>
 <10845a340607210208l2ffea986ndd77a0a0c50a9965@mail.gmail.com>
 <44C09BE2.7000201@php.net>
X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl'
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness
From: derick@php.net (Derick Rethans)

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.

regards,
Derick