Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25101 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80046 invoked by uid 1010); 2 Aug 2006 07:40:38 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 80031 invoked from network); 2 Aug 2006 07:40:38 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 2 Aug 2006 07:40:38 -0000 X-PHP-List-Original-Sender: derick@php.net X-Host-Fingerprint: 82.94.239.5 jdi.jdi-ict.nl Linux 2.5 (sometimes 2.4) (4) Received: from ([82.94.239.5:60955] helo=jdi.jdi-ict.nl) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 1B/20-45114-5F650D44 for ; Wed, 02 Aug 2006 03:40:37 -0400 Received: from localhost (localhost [127.0.0.1]) by jdi.jdi-ict.nl (8.13.6/8.12.11) with ESMTP id k727eYND031250; Wed, 2 Aug 2006 09:40:34 +0200 Date: Wed, 2 Aug 2006 09:40:22 +0200 (CEST) X-X-Sender: derick@localhost To: Lukas Smith cc: internals@lists.php.net In-Reply-To: <86.FD.45114.BAC40D44@pb1.pair.com> Message-ID: References: <18810497049.20060801234124@marcus-boerger.de> <44CFDB2B.1010907@cschneid.com> <20060802010156.5be0258c@pierre-u64> <44CFDF89.6010506@lerdorf.com> <86.FD.45114.BAC40D44@pb1.pair.com> X-Face: "L'&?Ah3MYF@FB4hU'XhNhLB]222(Lbr2Y@F:GE[OO;"F5p>qtFBl|yVVA&D{A(g3[C}mG:199P+5C'v.M/u@Z\![0b:Mv.[l6[uWl' MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness From: derick@php.net (Derick Rethans) On Wed, 2 Aug 2006, Lukas Smith wrote: > 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? Not really, but it's never too late to learn how something really works. If you want to cater for everybody that thinks that OO support was there in PHP 4 you're quite lost already :) regards, Derick