Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25099
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <86.FD.45114.BAC40D44@pb1.pair.com>
To: internals@lists.php.net
Date: Wed, 02 Aug 2006 08:56:42 +0200
User-Agent: Thunderbird 1.5.0.5 (Windows/20060719)
MIME-Version: 1.0
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>
In-Reply-To: <44CFDF89.6010506@lerdorf.com>
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)

Rasmus Lerdorf wrote:

> Relax people.  There are certain paradigms and expectations people have. 
>   The original PHP design met the expectations and paradigms of a 
> loosely typed procedural language.  Now, some 12 years later we are 
> trying to meet a new class of expectations.  We have kids coming out of 
> universities today who barely know what procedural programming is.  All 
> they know is OOP and we want to give them something that meets their 
> expectations.  We have to be careful that we don't ignore too many OOP 
> rules or we would fail to meet these expectations.  The PHP way is not 
> to make everything look like the procedural approach.  The PHP way is to 
> cater to peoples' existing knowledge and build a language that does what 
> people expect it to.  That doesn't mean we shouldn't loosen up some OOP 
> rules where it makes sense, but it also doesn't mean we should ignore 
> them completely.

sure .. and all the old users that have become used to how OOP in PHP 
works are to be ignored?

regards,
Lukas