Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:25238 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 40127 invoked by uid 1010); 7 Aug 2006 18:29:10 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 40112 invoked from network); 7 Aug 2006 18:29:10 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Aug 2006 18:29:10 -0000 X-PHP-List-Original-Sender: ceo@l-i-e.com X-Host-Fingerprint: 67.139.134.202 o2.hostbaby.com FreeBSD 4.7-5.2 (or MacOS X 10.2-10.3) (2) Received: from ([67.139.134.202:2507] helo=o2.hostbaby.com) by pb1.pair.com (ecelerity 2.1.1.3 r(11751M)) with ESMTP id 62/AB-27091-57687D44 for ; Mon, 07 Aug 2006 14:29:10 -0400 Received: (qmail 72041 invoked by uid 98); 7 Aug 2006 18:29:10 -0000 Received: from 127.0.0.1 by o2.hostbaby.com (envelope-from , uid 1013) with qmail-scanner-1.25 ( Clear:RC:1(127.0.0.1):. Processed in 0.117049 secs); 07 Aug 2006 18:29:10 -0000 X-Qmail-Scanner-Mail-From: ceo@l-i-e.com via o2.hostbaby.com X-Qmail-Scanner: 1.25 (Clear:RC:1(127.0.0.1):. Processed in 0.117049 secs) Received: from unknown (HELO l-i-e.com) (127.0.0.1) by localhost with SMTP; 7 Aug 2006 18:29:09 -0000 Received: from 67.108.68.40 (SquirrelMail authenticated user ceo@l-i-e.com) by www.l-i-e.com with HTTP; Mon, 7 Aug 2006 13:29:09 -0500 (CDT) Message-ID: <29391.67.108.68.40.1154975349.squirrel@www.l-i-e.com> In-Reply-To: <33b17cf921c0b08ca914f98d39644c0c@procata.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> Date: Mon, 7 Aug 2006 13:29:09 -0500 (CDT) To: "PHP Developers Mailing List" Reply-To: ceo@l-i-e.com User-Agent: Hostbaby Webmail MIME-Version: 1.0 Content-Type: text/plain;charset=iso-8859-1 Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) Importance: Normal Subject: Re: [PHP-DEV] RfC: rethink OO inheritance strictness From: ceo@l-i-e.com ("Richard Lynch") 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