Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25239 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 55401 invoked by uid 1010); 7 Aug 2006 19:00:56 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 55385 invoked from network); 7 Aug 2006 19:00:56 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Aug 2006 19:00:56 -0000 X-PHP-List-Original-Sender: helly@php.net X-Host-Fingerprint: 81.169.182.136 ajaxatwork.net Linux 2.4/2.6 Received: from ([81.169.182.136:34009] helo=strato.aixcept.de) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 42/6D-27091-5ED87D44 for ; Mon, 07 Aug 2006 15:00:54 -0400 Received: from [192.168.1.3] (dslb-084-063-031-028.pools.arcor-ip.net [84.63.31.28]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (No client certificate requested) by strato.aixcept.de (Postfix) with ESMTP id 343C435C1F5; Mon, 7 Aug 2006 21:00:47 +0200 (CEST) Date: Mon, 7 Aug 2006 21:00:48 +0200 Reply-To: Marcus Boerger X-Priority: 3 (Normal) Message-ID: <981573438.20060807210048@marcus-boerger.de> To: Richard Lynch Cc: PHP Developers Mailing List In-Reply-To: <29391.67.108.68.40.1154975349.squirrel@www.l-i-e.com> 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> <29391.67.108.68.40.1154975349.squirrel@www.l-i-e.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness From: helly@php.net (Marcus Boerger) Hello Richard, strict would meann a new keyword which most likely breaks a bunch of applications. It would be much easier to do: class Foo implements Strict { } and for the methods only stick with 'interface'. best regards marcus Monday, August 7, 2006, 8:29:09 PM, you wrote: > On Mon, August 7, 2006 8:25 am, 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' >> >> 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. > strict class blah blah blah { } > as shorthand for: > class blah blah blah { [strict function (){}]* } > doesn't seem like it would be too terribly difficult to implement or > understand... > Though 'strict' may not be the right keyword... > method_signature_match is a bit too verbose, though :-) > sigmatch ??? > 'strict' just has too many other potential meanings... > -- > Like Music? > http://l-i-e.com/artists.htm Best regards, Marcus