Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:28886
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 66.249.92.175 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Fh/zVatknOCelF8QR6vN2FpFrMrCG33Ce0UtvolEyE00Q4IvadbZtFEKzQJIr5nQ6/8tUJRIcw9aATG2S/S2mEIlZlmV+gEA6ctL0MFCr9iI3uDPKbxMjJBphUWx/pDT5BF5b/HI0qVdxGrIST6dudnDqqvW/53BJgbc75grbo4=
Message-ID: <7f3ed2c30704170615q18997fbv39acc92ea24a50c8@mail.gmail.com>
Date: Tue, 17 Apr 2007 15:15:27 +0200
To: "Christian Schneider" <cschneid@cschneid.com>
Cc: internals@lists.php.net
In-Reply-To: <4624C68A.8030402@cschneid.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; 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>
Subject: Re: [PHP-DEV] PHP6 todo list (E_STRICT in E_ALL)
From: hannes.magnusson@gmail.com ("Hannes Magnusson")

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

>
> I'm with Lukas there about the E_STRICT/E_DEPRECATED split but I'm not
> even sure if E_DEPRECATED should be included in E_ALL: It depends on how
> liberally things will get marked E_DEPRECATED.
>
> - Chris
>