Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25141
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7.0.1.0.2.20060802201553.0a02bc28@zend.com>
Date: Wed, 02 Aug 2006 20:16:48 +0300
To: Rasmus Lerdorf <rasmus@lerdorf.com>
Cc: pierre.php@gmail.com,internals@lists.php.net,
 Christian Schneider <cschneid@cschneid.com>
In-Reply-To: <44D0DB82.1070307@lerdorf.com>
References: <EB.71.29121.B6690C44@pb1.pair.com>
 <18810497049.20060801234124@marcus-boerger.de>
 <44CFDB2B.1010907@cschneid.com>
 <20060802010156.5be0258c@pierre-u64>
 <44CFDF89.6010506@lerdorf.com>
 <7.0.1.0.2.20060802153119.0c2193c0@zend.com>
 <44D0DB82.1070307@lerdorf.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness
From: zeev@zend.com (Zeev Suraski)

At 20:06 02/08/2006, Rasmus Lerdorf wrote:
>Zeev Suraski wrote:
>>I believe the problem is that 10 years ago we introduced what can 
>>be described as 'loose OO programming', and we're replacing it 
>>(instead of augmenting it) with strict OO programming.
>
>Sure, and I agree that we should find a comfortable middleground, 
>I'd just like to see a little less criticism of Marcus and some more 
>civilized discussion.  As far as I am concerned, Marcus' approach of 
>making the existing OOP design consistent with conventional OOP 
>principles is an extremely valuable one and something I hope he will 
>continue doing despite all the crap he takes for it.  By going 
>through this we see where we diverge and we can make deliberate 
>decisions to loosen things up where it makes sense.

Agreed - I definitely value Marcus' great contributions to PHP.  He 
does need to be balanced every one in a while :)

>In this particular case I think it should be possible to mark 
>certain internal methods as strict and keep userspace methods loose.

Great, so we agree.

Zeev