Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:25090
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <44CFDF89.6010506@lerdorf.com>
Date: Tue, 01 Aug 2006 16:11:05 -0700
User-Agent: Thunderbird 1.5.0.5 (Macintosh/20060719)
MIME-Version: 1.0
To: pierre.php@gmail.com
CC: internals@lists.php.net, Christian Schneider <cschneid@cschneid.com>
References: <EB.71.29121.B6690C44@pb1.pair.com>	<18810497049.20060801234124@marcus-boerger.de>	<44CFDB2B.1010907@cschneid.com> <20060802010156.5be0258c@pierre-u64>
In-Reply-To: <20060802010156.5be0258c@pierre-u64>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness
From: rasmus@lerdorf.com (Rasmus Lerdorf)

Pierre wrote:
> On Wed, 02 Aug 2006 00:52:27 +0200
> cschneid@cschneid.com (Christian Schneider) wrote:
> 
> 
>> Why can't we agree that people use classes in different ways (call it 
>> non-OO ways if you want) and restrain from forcing ones views onto 
>> everybody? PHP works well because it of the freedom it gives, not 
>> because of the limitations.
> 
> <rant>
> Because there is people who does not want to know the PHP way. They
> want their {put your fashion OO language here} way in PHP. Strictness
> was never a goal in php.
> 
> But it looks like the opinion of the current php users do not matter,
> only the ones coming from {put your fashion OO language here}. It seems
> that they have hard time to justify the usage of {put your fashion OO
> language here}, time to bork PHP.
> </rant>

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.

-Rasmus