Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:45436
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 72.14.220.155 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=RXbWuJouO6BFkNZhT2BF+Ur+01NcbcHpFVFiJfc8r71D9XajoJKNjCWoqmYerWSMoM
         WEylg7w+/vujCCNJ7kLY8ntjqTCiylROxvGu8y3bnSt55y7N3sd/dHkmlsGIMPRHvgFX
         gUsGgf/E+qF6DwvzsgJJSfjswWO7GbfcahJ4g=
MIME-Version: 1.0
Date: Sun, 30 Aug 2009 23:06:10 +0200
Message-ID: <fe05d1540908301406h6ccde718o51383a55e5b4949@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: text/plain; charset=ISO-8859-1
Subject: silent startup errors msg about deprecated (or other) warnings
From: pierre.php@gmail.com (Pierre Joye)

Hi,

While trying to fix some tests, I found that display_startup_errors is
ignored by some startup errors like deprecated ini settings. Using:

php  -d display_startup_errors=0 -d safe_mode=1 foo.php

a deprecated warning will be reaised. I think it is not the expected
behavior and consider that as a bug.

The problem is that we try to log the message and if not log backed
are available, we fall back to the sapi's log_message. In case of CLI,
it is a simple fprintf to STDERR. This simple patch should fix the
problem http://pastie.org/599790.

Any objection to the idea? I can adapt it to the other SAPI if
necessary as well as update the affected tests (like
putenv_err1.phpt).


Cheers,
-- 
Pierre

http://blog.thepimp.net | http://www.libgd.org