Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25121
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <7.0.1.0.2.20060802160436.0d046278@zend.com>
Date: Wed, 02 Aug 2006 16:09:58 +0300
To: Derick Rethans <derick@php.net>
Cc: PHP Developers Mailing List <internals@lists.php.net>
In-Reply-To: <Pine.LNX.4.62.0608021448540.26373@localhost>
References: <EB.71.29121.B6690C44@pb1.pair.com>
 <18810497049.20060801234124@marcus-boerger.de>
 <1154478748.6599.16.camel@blobule>
 <Pine.LNX.4.62.0608020940590.26373@localhost>
 <7.0.1.0.2.20060802153332.0ce21c00@zend.com>
 <Pine.LNX.4.62.0608021448540.26373@localhost>
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 15:49 02/08/2006, Derick Rethans wrote:
>On Wed, 2 Aug 2006, Zeev Suraski wrote:
>
> > At 10:41 02/08/2006, Derick Rethans wrote:
> > >
> > >Yeah, but PHP 4 didn't have OO support, so that argument doesn't count.
> >
> > It sure as hell did.
>
>You can hardly call an array with another table with function pointers
>OO :)

Watch me :)  The fact of the matter is that people used this 
infrastructure in an object oriented way.  It wasn't exactly 
Smalltalk or Java, but many developers used it to implement some of 
the more common OO practices (encapsulation, inheritence).  I guess 
you could call it 'cooperative OO' (a-la Windows 3.x's cooperative 
multitasking).

Anyway, whatever we call it, it's a fact that a lot of people are 
using it.  I think it's more than reasonable to assume that if 
several people here on the relatively purist internals@ say they'd 
want to go on using it, there are many like them in the PHP 
userbase.  Finding a compromise that gives both 'camps' a workable 
solution makes the most sense here.

Zeev