Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:9403 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 53553 invoked by uid 1010); 19 Apr 2004 21:48:43 -0000 Delivered-To: ezmlm-scan-internals@lists.php.net Delivered-To: ezmlm-internals@lists.php.net Received: (qmail 53475 invoked from network); 19 Apr 2004 21:48:42 -0000 Received: from unknown (HELO xaxa.search.ch) (195.141.85.118) by pb1.pair.com with SMTP; 19 Apr 2004 21:48:42 -0000 Received: from localhost (localhost [127.0.0.1]) by xaxa.search.ch (Postfix) with ESMTP id 73B2D6D867; Mon, 19 Apr 2004 23:48:42 +0200 (CEST) Received: by xaxa.search.ch (Postfix, from userid 65534) id 638546D85F; Mon, 19 Apr 2004 23:48:41 +0200 (CEST) Received: from cschneid.com (ultrafilter2-i [192.168.85.3]) by xaxa.search.ch (Postfix) with ESMTP id 7F8C66D85A; Mon, 19 Apr 2004 23:48:40 +0200 (CEST) Message-ID: <40844937.2020200@cschneid.com> Date: Mon, 19 Apr 2004 23:48:39 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040114 X-Accept-Language: en-us, en, de-ch, de MIME-Version: 1.0 To: George Schlossnagle Cc: Marcus Boerger , Zeev Suraski , Andi Gutmans , internals@lists.php.net References: <5.1.0.14.2.20040419112627.03efaa00@localhost> <5.1.0.14.2.20040419130523.04e3fe60@localhost> <101121849562.20040419204933@marcus-boerger.de> <0EB7FB18-923B-11D8-8782-000393B2B3C0@omniti.com> <40844688.5040701@cschneid.com> In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on xaxa.search.ch X-Spam-Level: X-Spam-Status: No, hits=-4.9 required=5.0 tests=BAYES_00 autolearn=ham version=2.63 X-Virus-Scanned: by AMaViS 0.3.12pre8 Subject: Re: [PHP-DEV] Interface inheritance From: cschneid@cschneid.com (Christian Schneider) George Schlossnagle wrote: >>>>> 1. First of all, I agree that in a perfect world we should go with >>>>> E_COMPILE_ERROR for everything. Maybe now that's constructors are >>> >>> +1 >> >> Are you guys serious about a compile error if I override a method with >> different parameters? This must be the mailing list of a different >> language than PHP... > > If you override an interface with a different number of parameters or > with incorrectly typed parameters, yes. I agree there but 1. was saying _everything_, that included more than just interfaces and abstract classes. That's why I'm asking if you're serious. Let's recap: a) People agree to be strict for *interfaces* and *abstract classes*. b) There was a proposal to also give a compile error for normal methods. I'm not sure if people who gave a +1 here really meant it. - Chris