Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:63863 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 80435 invoked from network); 14 Nov 2012 06:42:50 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 14 Nov 2012 06:42:50 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.153 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.153 smtp153.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.153] ([67.192.241.153:52870] helo=smtp153.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id A0/6C-30200-96D33A05 for ; Wed, 14 Nov 2012 01:42:49 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp15.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 551573006A3; Wed, 14 Nov 2012 01:42:46 -0500 (EST) X-Virus-Scanned: OK Received: by smtp15.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id E412F300561; Wed, 14 Nov 2012 01:42:45 -0500 (EST) Message-ID: <50A33D65.2020202@sugarcrm.com> Date: Tue, 13 Nov 2012 22:42:45 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:16.0) Gecko/20121010 Thunderbird/16.0.1 MIME-Version: 1.0 To: Adam Harvey CC: Christopher Jones , PHP internals References: <50A197D2.5070307@oracle.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] RFC: ext/mysql deprecation From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! >> 2. Mention how to turn off E_DEPRECATED warnings in the RFC? > > Done and done. I've added a (short) workarounds section towards the > bottom, which can be moved up later if the RFC is accepted. Please note currently PHP has no mechanism of turning off any warnings or errors. The best you can do is to cause them not be printed. However, any tool that intercepts error messages still sees them, they still consume resources when produced, still may break unit tests if you're not aware of them and they convert errors to failures like PHPUnit does, still will break any code that sets it's won error reporting if it doesn't remember to disable deprecated messages, etc. So adding warnings hurts performance and may hurt functionality even if you don't see them. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227