Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:45362 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 46997 invoked from network); 24 Aug 2009 21:51:11 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 24 Aug 2009 21:51:11 -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 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:33395] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 65/08-03363-D4B039A4 for ; Mon, 24 Aug 2009 17:51:10 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id 5F2654144059; Mon, 24 Aug 2009 21:52:57 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D-hDRoYPscCu; Mon, 24 Aug 2009 23:52:53 +0200 (CEST) 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 bigtime.backendmedia.com (Postfix) with ESMTP id D0D0C4144009; Mon, 24 Aug 2009 23:52:52 +0200 (CEST) Cc: jani.taskinen@iki.fi, Ilia Alshanetsky , 'PHP Internals' Message-ID: <250F0E93-D6F2-490F-9129-598AC6E96500@pooteeweet.org> To: Stanislav Malyshev In-Reply-To: <4A930956.9070709@zend.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v936) Date: Mon, 24 Aug 2009 23:51:01 +0200 References: <4A92D936.2010107@zend.com> <9E8BD3A3-8915-4492-88A9-7EA1A0CF6D86@prohost.org> <4A92DC60.2050606@zend.com> <4A92EA60.6020605@zend.com> <4A92F13B.9000204@zend.com> <4A92FFA8.1060401@zend.com> <4A9304FC.2000906@sci.fi> <4A930956.9070709@zend.com> X-Mailer: Apple Mail (2.936) Subject: Re: [PHP-DEV] [patch] error masks From: mls@pooteeweet.org (Lukas Kahwe Smith) On 24.08.2009, at 23:42, Stanislav Malyshev wrote: > Hi! > >> Quite boring to read this thread where two persons argue about >> something abstract. Stas, can you give a real life example where >> your patch is necessary..? > > Any code where you either use @ or error_reporting which is not -1 > would benefit from it by not processing errors that go nowhere. I > just looked at Zend Framework - with is pretty clean with regard to > E_NOTICE/E_STRICT problems - and @ is used in dozens of classes > around. The speedup would be probably not very big for whole RL > application, but it's a 10-line patch, and little things help too. well a few of those places would probably be fixable, by providing functions to check beforehand if calling the final function would cause an error. but that if course would add more overhead, but would still be the "cleaner" solution. overall i am not so convinced about the ignoring approach. as for E_STRICT .. that shouldnt become less of an issue now that we have E_DEPRECATED .. but i guess that just means that in the future people will complain about E_DEPRECATED .. anyways to me both E_STRICT and E_DEPRECATED are development tools that can be totally ignored in production. however E_NOTICE should not occur in production and we shouldnt encourage people to make them disappear entirely. regards, Lukas Kahwe Smith mls@pooteeweet.org