Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54169 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 68379 invoked from network); 23 Jul 2011 22:22:20 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2011 22:22:20 -0000 Authentication-Results: pb1.pair.com header.from=pierre.php@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=pierre.php@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.220.170 as permitted sender) X-PHP-List-Original-Sender: pierre.php@gmail.com X-Host-Fingerprint: 209.85.220.170 mail-vx0-f170.google.com Received: from [209.85.220.170] ([209.85.220.170:52014] helo=mail-vx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 70/71-59700-A994B2E4 for ; Sat, 23 Jul 2011 18:22:19 -0400 Received: by vxi39 with SMTP id 39so2566392vxi.29 for ; Sat, 23 Jul 2011 15:22:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=z0aJHSQberPOjrok6ABhra+j732UOMsGNU5DlMkYhic=; b=ktWka++ARIiggHiqqC7xf6JCRGANHnxL+GeOJV0aYFoI6CHFDAVcpiXtvmny2fhgD+ g+pAc06W0QbHNGOeyBzIwW2IoJZxRmiKIrOqr03uN0EkFylnMnA2qZUKMgSWXoDlipjd mEi+VJkOe32s72/n+7Kyv/EKSh1li8iClC/+I= MIME-Version: 1.0 Received: by 10.52.173.210 with SMTP id bm18mr2895904vdc.438.1311459734180; Sat, 23 Jul 2011 15:22:14 -0700 (PDT) Received: by 10.52.162.129 with HTTP; Sat, 23 Jul 2011 15:22:14 -0700 (PDT) In-Reply-To: <4E2B420C.3030203@sugarcrm.com> References: <4E2B420C.3030203@sugarcrm.com> Date: Sun, 24 Jul 2011 00:22:14 +0200 Message-ID: To: Stas Malyshev Cc: PHP Internals Content-Type: text/plain; charset=ISO-8859-1 Subject: Re: [PHP-DEV] E_STRICT in production From: pierre.php@gmail.com (Pierre Joye) hi Stas, The idea of E_STRICT when we introduced it was to help developers. So I tend to think that we should not enable it in php.ini-production. On Sat, Jul 23, 2011 at 11:50 PM, Stas Malyshev wrote: > Hi! > > 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. > -- > Stanislav Malyshev, Software Architect > SugarCRM: http://www.sugarcrm.com/ > (408)454-6900 ext. 227 > > -- > PHP Internals - PHP Runtime Development Mailing List > To unsubscribe, visit: http://www.php.net/unsub.php > > -- Pierre @pierrejoye | http://blog.thepimp.net | http://www.libgd.org