Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:47627 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 1381 invoked from network); 25 Mar 2010 22:31:03 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 25 Mar 2010 22:31:03 -0000 Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 188.40.37.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 188.40.37.16 hq1.backendmedia.com Linux 2.6 Received: from [188.40.37.16] ([188.40.37.16:52006] helo=hq1.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 22/12-25388-624EBAB4 for ; Thu, 25 Mar 2010 17:31:03 -0500 Received: from localhost (unknown [127.0.0.1]) by hq1.backendmedia.com (Postfix) with ESMTP id 7D6572E30011; Thu, 25 Mar 2010 22:30:58 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from hq1.backendmedia.com ([127.0.0.1]) by localhost (hq1.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id aBK2WtKuGfnT; Thu, 25 Mar 2010 23:30:58 +0100 (CET) Received: from [192.168.0.151] (217-162-131-234.dclient.hispeed.ch [217.162.131.234]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by hq1.backendmedia.com (Postfix) with ESMTPSA id 415592E3000E; Thu, 25 Mar 2010 23:30:58 +0100 (CET) Mime-Version: 1.0 (Apple Message framework v1077) Content-Type: text/plain; charset=us-ascii In-Reply-To: <8DFD21F2-E107-4E9C-9CAD-9BDFE276F633@stefan-marr.de> Date: Thu, 25 Mar 2010 23:30:59 +0100 Cc: PHP Developers Mailing List Content-Transfer-Encoding: quoted-printable Message-ID: References: <690D1362-7F1D-47B9-A4BF-EEA9CF38C5B0@pooteeweet.org> <8DFD21F2-E107-4E9C-9CAD-9BDFE276F633@stefan-marr.de> To: Stefan Marr X-Mailer: Apple Mail (2.1077) Subject: Re: [PHP-DEV] horizontal reuse: traits vs. grafts From: mls@pooteeweet.org (Lukas Kahwe Smith) On 25.03.2010, at 21:13, Stefan Marr wrote: > On 24 Mar 2010, at 11:50, Lukas Kahwe Smith wrote: >> "In case of the above definition of Talker, PHP will show a warning = that there have been conflicts and name the methods smallTalk() and = bigTalk() as the reason of this conflict. Therefore, neither of the = given implementations will be available in the class." >>=20 >> I think this is a fundamental decision, should it be a warning or a = fatal error? Generally I prefer PHP to keep on going whenever it can. I = guess in most cases if we stick to a warning the user will end up with a = fatal error anyway, but it might not be so clear why the given method is = unavailable. But there should still be a warning, which I guess cannot = be suppressed all that easily. > Well, I do not like a fatal errors. This problem does not leave the = engine in an undefined state, and personally, I think, fatals should = only be caused by something which really cannot be handled. >=20 > Since we have __call, there might even be something executable. Yeah, I agree, just wanted to bring this point up. I am right that this = warning cannot be suppressed via some @ magic and so if at all would = need to be suppressed by a custom error handler? regards, Lukas Kahwe Smith mls@pooteeweet.org