Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:24809 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 26336 invoked by uid 1010); 21 Jul 2006 09:18:37 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 26320 invoked from network); 21 Jul 2006 09:18:37 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 21 Jul 2006 09:18:37 -0000 X-PHP-List-Original-Sender: lsmith@php.net X-Host-Fingerprint: 212.112.227.169 ipx11223.ipxserver.de Linux 2.5 (sometimes 2.4) (4) Received: from ([212.112.227.169:36810] helo=ipx11223.ipxserver.de) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 13/73-29121-AEB90C44 for ; Fri, 21 Jul 2006 05:18:37 -0400 Received: from localhost (localhost [127.0.0.1]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 006FCDF00F4; Fri, 21 Jul 2006 12:01:23 +0200 (CEST) Received: from ipx11223.ipxserver.de ([127.0.0.1]) by localhost (flottensignalgeber [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27161-08; Fri, 21 Jul 2006 12:01:21 +0200 (CEST) Received: from [127.0.0.1] (i577B481F.versanet.de [87.123.72.31]) by ipx11223.ipxserver.de (Postfix) with ESMTP id 6ABE6DF000E; Fri, 21 Jul 2006 12:01:21 +0200 (CEST) Message-ID: <44C09BE2.7000201@php.net> Date: Fri, 21 Jul 2006 11:18:26 +0200 User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: RQuadling@GoogleMail.com Cc: Michael Wallner , internals@lists.php.net References: <10845a340607210208l2ffea986ndd77a0a0c50a9965@mail.gmail.com> In-Reply-To: <10845a340607210208l2ffea986ndd77a0a0c50a9965@mail.gmail.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by somedaemon at backendmedia.com Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness From: lsmith@php.net (Lukas Smith) 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. regards, Lukas