Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25232 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 84517 invoked by uid 1010); 7 Aug 2006 14:47:25 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 84502 invoked from network); 7 Aug 2006 14:47:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Aug 2006 14:47:25 -0000 X-Host-Fingerprint: 87.123.84.181 i577B54B5.versanet.de Received: from ([87.123.84.181:28003] helo=localhost.localdomain) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 5E/0D-27091-B7257D44 for ; Mon, 07 Aug 2006 10:47:25 -0400 To: internals@lists.php.net,Jeff Moore Message-ID: <44D75278.2080204@php.net> Date: Mon, 07 Aug 2006 16:47:20 +0200 User-Agent: Thunderbird 1.5.0.5 (Windows/20060719) MIME-Version: 1.0 CC: Derick Rethans , Rasmus Lerdorf 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> <33b17cf921c0b08ca914f98d39644c0c@procata.com> In-Reply-To: <33b17cf921c0b08ca914f98d39644c0c@procata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Posted-By: 87.123.84.181 Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness From: lsmith@php.net (Lukas Smith) Jeff Moore wrote: > > On Aug 4, 2006, at 3:23 AM, Derick Rethans wrote: > >> - Add a new flag to methods (at the implementation level) that will >> allow to flag them as 'strict' > > Hello, > > Would exposing this flag to the user at method level get a bit verbose > for those who want to use it? Perhaps a class level flag for all > methods? Wasn't that proposed earlier? Its a long thread to follow, > forgive me if I've missed something. Yeah if we do allow a flag for methods, then we should also have one for the entire class. But if we reuse the "interface" keyword things will get tricky. I doubt the strict camp wants to allow people to add method bodies in interfaces and "class interface foo {}" looks odd too. regards, Lukas