Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:54215
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: error (pb1.pair.com: domain analysisandsolutions.com from 166.84.1.89 cause and error)
Date: Tue, 26 Jul 2011 12:52:04 -0400
To: PHP Internals List <internals@lists.php.net>
Message-ID: <20110726165203.GA6599@panix.com>
References: <4E2B420C.3030203@sugarcrm.com>
 <CAH-PCH5h090x77f1mu4_8Q250uOs7B6HBqWR_nStJCGeVX9iOA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <CAH-PCH5h090x77f1mu4_8Q250uOs7B6HBqWR_nStJCGeVX9iOA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)
Subject: Re: [PHP-DEV] E_STRICT in production
From: danielc@analysisandsolutions.com (Daniel Convissor)

Hi Folks:

On Sun, Jul 24, 2011 at 12:18:51AM +0200, Ferenc Kovacs wrote:
> 
> 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.

I'm thinking similarly.  Strict is totaly unimportant in production.
Deprecated warnings, on the other hand, can be helpful in production.
We all have some bits of code that only gets reached in unusual
circumstances.  Those situations often only arise in production.
Getting told about them can be a good thing.

Thanks,

--Dan

-- 
 T H E   A N A L Y S I S   A N D   S O L U T I O N S   C O M P A N Y
            data intensive web and database programming
                http://www.AnalysisAndSolutions.com/
 4015 7th Ave #4, Brooklyn NY 11232  v: 718-854-0335 f: 718-854-0409