Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:54168 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 67000 invoked from network); 23 Jul 2011 22:18:57 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jul 2011 22:18:57 -0000 Authentication-Results: pb1.pair.com smtp.mail=tyra3l@gmail.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=tyra3l@gmail.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.170 as permitted sender) X-PHP-List-Original-Sender: tyra3l@gmail.com X-Host-Fingerprint: 209.85.213.170 mail-yx0-f170.google.com Received: from [209.85.213.170] ([209.85.213.170:35745] helo=mail-yx0-f170.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 55/21-59700-0D84B2E4 for ; Sat, 23 Jul 2011 18:18:56 -0400 Received: by yxk8 with SMTP id 8so1988817yxk.29 for ; Sat, 23 Jul 2011 15:18:53 -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:content-transfer-encoding; bh=I377JgO1cs/EvyL0FHMeylkfH3gS9+12EE04kXeUW6c=; b=OkzizRe3IAo9uiUK7XJgsp6wM89hNC8d3i0v1/S25/uxrwotV/3gFnoCwX2GVD4ESq qLx8HmVKHQ52KRj3ahWTOGNOZ2D3kAaFwPXUKLGXOt7DZrikj+szxIA04KA25tbBpDf3 B17vjetm2taNd7iovnIxBrVa1pBaGZwwGQ63k= MIME-Version: 1.0 Received: by 10.236.155.41 with SMTP id i29mr3975648yhk.1.1311459531787; Sat, 23 Jul 2011 15:18:51 -0700 (PDT) Received: by 10.147.167.6 with HTTP; Sat, 23 Jul 2011 15:18:51 -0700 (PDT) In-Reply-To: <4E2B420C.3030203@sugarcrm.com> References: <4E2B420C.3030203@sugarcrm.com> Date: Sun, 24 Jul 2011 00:18:51 +0200 Message-ID: To: Stas Malyshev Cc: PHP Internals Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [PHP-DEV] E_STRICT in production From: tyra3l@gmail.com (Ferenc Kovacs) On Sat, Jul 23, 2011 at 11:50 PM, Stas Malyshev wr= ote: > 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. I think no. first of all, 1 think it would be better to change only one thing at a time (add E_STRICT to E_ALL), and we also exclude E_DEPRECATED for production, which would imo much more important for most apps than fixing the E_STRICT problems. --=20 Ferenc Kov=C3=A1cs @Tyr43l - http://tyrael.hu