Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:44354
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Message-ID: <EC.C1.58950.8F15A3A4@pb1.pair.com>
To: internals@lists.php.net
Date: Thu, 18 Jun 2009 18:40:56 +0400
Lines: 58
Subject: bug #48583 or display_errors saga
From: dmda@yandex.ru ("jvlad")

If the bug #48583 can't be accepted through bugs.php.net, I think it makes 
sense to discuss it here.

In short the question is:
Should display_errors and the other error-routing settings work or not?

I belive they are very important and should always work.
Just my 2cents.


Long story:
display_errors=off setting won't stop some errors from appearing in the
output.

Any errors thrown by modules at the initialization phase shoud be
accumulated somewhere, not passed to the output directly.
In partcilar, if you have an error in php.ini, display_errors=OFF won't
have any effect.

Reproduce code:
---------------
php.ini:
=======================================
error_reporting=E_ALL | E_DEPRECATED
error_log="D:\php-5.3RC3-Win32\php.log"
log_errors=On
display_errors=Off
#something
;a comment
=======================================

command line:
=======================================
php-cgi.exe -i >somefile.html
=======================================

Expected result:
----------------
nothing in the output

Actual result:
--------------
2 errors appeared on screen:

PHP Deprecated:  Comments starting with '#' are deprecated in
D:\php-5.3RC3-Win32\php.ini on line 5
in Unknown on line 0

PHP Warning:  Unknown: It is not safe to rely on the system's timezone
settings. You are *required*
to use the date.timezone setting or the date_default_timezone_set()
function. In case you used any o
f those methods and you are still getting this warning, you most likely
misspelled the timezone iden
tifier. We selected 'Europe/Moscow' for '4.0/DST' instead in Unknown on
line 0