On 17/04/07, Hannes Magnusson <[EMAIL PROTECTED]> wrote:
On 4/17/07, Christian Schneider <[EMAIL PROTECTED]> 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!"
--
PHP Internals - PHP Runtime Development Mailing List
To unsubscribe, visit: http://www.php.net/unsub.php
