Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:50891 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 59126 invoked from network); 7 Dec 2010 11:58:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 7 Dec 2010 11:58:58 -0000 Authentication-Results: pb1.pair.com header.from=php@stefan-marr.de; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=php@stefan-marr.de; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain stefan-marr.de from 85.88.12.247 cause and error) X-PHP-List-Original-Sender: php@stefan-marr.de X-Host-Fingerprint: 85.88.12.247 toolslave.net Received: from [85.88.12.247] ([85.88.12.247:50833] helo=uhweb12247.united-hoster.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id FF/62-40992-0812EFC4 for ; Tue, 07 Dec 2010 06:58:56 -0500 Received: from soft83.vub.ac.be ([134.184.43.183]) by uhweb12247.united-hoster.com with esmtpsa (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.69) (envelope-from ) id 1PPwBi-00057v-12; Tue, 07 Dec 2010 12:58:32 +0100 Mime-Version: 1.0 (Apple Message framework v1082) Content-Type: text/plain; charset=us-ascii In-Reply-To: <20101205155313.421aa981@benny-pc> Date: Tue, 7 Dec 2010 12:58:43 +0100 Cc: internals@lists.php.net Content-Transfer-Encoding: quoted-printable Message-ID: <2D046736-6623-4B40-BCF2-97D5524DF86F@stefan-marr.de> References: <20101205155313.421aa981@benny-pc> To: Benjamin Eberlei X-Mailer: Apple Mail (2.1082) Subject: Re: [PHP-DEV] Traits and Conflicts: Collisions as Warnings or Fatal? From: php@stefan-marr.de (Stefan Marr) Hi: On 05 Dec 2010, at 15:53, Benjamin Eberlei wrote: > I wondered before why this only triggers a warning. A fatal error = sounds good at that point in my opinion. >=20 > It is comparable to interfaces/Abstract classes being implemented = wrong and this also leads to a fatal error. Additionally there is no way = this "just" happens to your code. You have to make changes to a trait = explicitly to trigger this problem, so this is only happening in = development. So, that is the way to go? The original idea to go with a warning was, that it is not the case that = the engine is in an unrecoverable state, thus, the code actually will = work in that case, but perhaps produce unexpected results. In general, PHP uses fatals far to often for my taste, but well, to keep = it consistent, we can go fatal here, too. Is there a general consensus on that? Thanks Stefan --=20 Stefan Marr Software Languages Lab Vrije Universiteit Brussel Pleinlaan 2 / B-1050 Brussels / Belgium http://soft.vub.ac.be/~smarr Phone: +32 2 629 2974 Fax: +32 2 629 3525