Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28888
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain googlemail.com designates 66.249.92.172 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=googlemail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=G2cLVN0BPlKmPDPFyPbR6Vil7z/mNZlAbaGEisMHnIucQx/cj968jCE5N8jUzUHfENdytTEOAKqZJxgr5DXfgwuH8RAouMquVSSHhdRDA5myqRYLxHLGNXvj/wfKCjlon7f0Kqr2vZMP7GiK43P0sbXGvj8kxw0UYpEKmyDJSfk=
Message-ID: <10845a340704170634i39d8c78bu3b461577ea148708@mail.gmail.com>
Date: Tue, 17 Apr 2007 14:34:28 +0100
Reply-To: RQuadling@GoogleMail.com
To: "Hannes Magnusson" <hannes.magnusson@gmail.com>
Cc: "Christian Schneider" <cschneid@cschneid.com>, internals@lists.php.net
In-Reply-To: <7f3ed2c30704170615q18997fbv39acc92ea24a50c8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <461E4437.2090105@pooteeweet.org> <46248872.3050503@pooteeweet.org>
	 <4624C05F.3060506@pooteeweet.org>
	 <7f3ed2c30704170552g7ab567bdhba64b2f1580b2c75@mail.gmail.com>
	 <4624C68A.8030402@cschneid.com>
	 <7f3ed2c30704170615q18997fbv39acc92ea24a50c8@mail.gmail.com>
Subject: Re: [PHP-DEV] PHP6 todo list (E_STRICT in E_ALL)
From: rquadling@googlemail.com ("Richard Quadling")

On 17/04/07, Hannes Magnusson <hannes.magnusson@gmail.com> wrote:
> On 4/17/07, Christian Schneider <cschneid@cschneid.com> wrote:
> > Hannes Magnusson wrote:
> > >> 7. add E_STRICT to E_ALL DONE (dmitry)
> > >
> > > My dictionary says that "all" means *all*, not "all except this and
> > > this and sometimes not that".
> >
> > E_ALL should have been called E_RECOMMENDED or E_DEFAULT to avoid this
> > confusion but in reality changing E_ALL to include everything would
> > unnecessarily break existing installations. I think we will have to live
> > with this misnomer and not try to 'fix' it.
>
> How exactly would any app break?
> You don't display errors on your production server, do you?
> It will only help you understand what is going on while you develop
> the application.
>
> I think what we need here is fix our php.ini files: php.ini-production
> & php.ini-developing
>
> -Hannes

In development mode I want to see every single
error/notice/warning/etc. How else am I supposed to know if I've done
something incorrect or the sand has shifted beneath my feet and I
didn't realise?

In production no errors should be displayed (i.e. all nice clean code)
but even if they are they should only be logged and not displayed.

So in both circumstances E_ALL should __still__ mean every single
error/notice/warning/etc.

I do like the idea of production and development ini files. That seems
to make more sense than recommended and dist. I'm sure dist means
distribution, but then what does recommended mean? Without knowing the
reason, seeing recommended and dist are confusing.

-- 
-----
Richard Quadling
Zend Certified Engineer : http://zend.com/zce.php?c=ZEND002498&r=213474731
"Standing on the shoulders of some very clever giants!"