Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54167 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 64824 invoked from network); 23 Jul 2011 22:07:53 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2011 22:07:53 -0000 Authentication-Results: pb1.pair.com smtp.mail=adam@adamharvey.name; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=adam@adamharvey.name; sender-id=pass Received-SPF: pass (pb1.pair.com: domain adamharvey.name designates 209.85.210.170 as permitted sender) X-PHP-List-Original-Sender: adam@adamharvey.name X-Host-Fingerprint: 209.85.210.170 mail-iy0-f170.google.com Received: from [209.85.210.170] ([209.85.210.170:39725] helo=mail-iy0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id BB/B0-59700-C264B2E4 for ; Sat, 23 Jul 2011 18:07:48 -0400 Received: by iym1 with SMTP id 1so3543954iym.29 for ; Sat, 23 Jul 2011 15:07:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=adamharvey.name; s=google; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=wu4xA+SoDo+LjhkPYg+BhDjycFXo6HiennQEmu7qCfk=; b=VVNx+ZctFWr+Srv82nA+mZje37iOf6hM0uMUf4h7LdrupdlSFYksIHUFVks/SpJ3t5 xKGa/QUBjMqySJ3PQSA3Wll9kQjY8HB/UtyAUHgbOVSFmrIa5yEnQNC9/ay3k3tANQbH UHrczTWUpt7czklWMxdE8XDFvjTjb24tDEHtk= MIME-Version: 1.0 Received: by 10.231.29.100 with SMTP id p36mr2886719ibc.123.1311458855523; Sat, 23 Jul 2011 15:07:35 -0700 (PDT) Sender: adam@adamharvey.name Received: by 10.231.168.71 with HTTP; Sat, 23 Jul 2011 15:07:35 -0700 (PDT) Received: by 10.231.168.71 with HTTP; Sat, 23 Jul 2011 15:07:35 -0700 (PDT) In-Reply-To: <4E2B420C.3030203@sugarcrm.com> References: <4E2B420C.3030203@sugarcrm.com> Date: Sat, 23 Jul 2011 15:07:35 -0700 X-Google-Sender-Auth: K3WWPqUej1pxRGKrHTQZAi5n2aU Message-ID: To: Stas Malyshev Cc: PHP Internals Content-Type: multipart/alternative; boundary=001517741b6a38950904a8c3cf85 Subject: Re: [PHP-DEV] E_STRICT in production From: aharvey@php.net (Adam Harvey) --001517741b6a38950904a8c3cf85 Content-Type: text/plain; charset=UTF-8 On Jul 23, 2011 2:51 PM, "Stas Malyshev" wrote: > Now that we've decided to add E_STRICT to E_ALL error mask, the question is - what should we put in recommended production INI - should we include E_STRICT or not? > Development has E_STRICT anyway, so no question there. I can't look it up easily at the moment, but assuming display_errors is off on the production configuration, I'd be inclined to make the error_reporting levels the same: that is, include E_STRICT. Adam --001517741b6a38950904a8c3cf85--