Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25208 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 41783 invoked by uid 1010); 6 Aug 2006 11:12:23 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 41768 invoked from network); 6 Aug 2006 11:12:23 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 6 Aug 2006 11:12:23 -0000 X-PHP-List-Original-Sender: zeev@zend.com X-Host-Fingerprint: 80.74.107.235 mail.zend.com Linux 2.5 (sometimes 2.4) (4) Received: from ([80.74.107.235:21091] helo=mail.zend.com) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id C8/88-06633-49EC5D44 for ; Sun, 06 Aug 2006 07:12:22 -0400 Received: (qmail 579 invoked from network); 6 Aug 2006 11:11:13 -0000 Received: from localhost (HELO zeev-notebook.zend.com) (127.0.0.1) by localhost with SMTP; 6 Aug 2006 11:11:13 -0000 Message-ID: <7.0.1.0.2.20060806141203.03cbf890@zend.com> X-Mailer: QUALCOMM Windows Eudora Version 7.0.1.0 Date: Sun, 06 Aug 2006 14:12:22 +0300 To: Lukas Smith Cc: internals@lists.php.net,Derick Rethans , Rasmus Lerdorf In-Reply-To: <44D2FC0D.3050009@php.net> References: <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> <44D1FAF0.5060906@lerdorf.com> <44D2FC0D.3050009@php.net> 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 10:49 04/08/2006, Lukas Smith wrote: >Derick Rethans wrote: > >>- Add a new flag to methods (at the implementation level) that >>will allow to flag them as 'strict' >>- In case such a strict method is improperly overridden - error >>out (E_ERROR) >>- In case a non-strict method is improperly overridden - emit E_STRICT > >i am fine with that proposal .. if we do split up E_STRICT into >E_STRICT (feature is not clean "proper" code) and E_DEPRECATED >(feature will be dropped in the next major release) > >also note that the first two points in Derick's list only apply to >classes on the C level .. userland classes will only trigger >E_STRICT if they are improperly overwritten. It's my list actually, so I'm definitely +1 on that :) Zeev