Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:118937
MIME-Version: 1.0
References: <CADDxozmK-qb37v1fE_j92UmO_y9XB2dt3rOmVxY4GdfUXwnoPg@mail.gmail.com>
 <42A5DAC6-253E-478D-808C-36690FA88315@gmail.com> <CADDxoz=z2kQsx2cq5FxQyBM4r+zDOcAoK035RqM811PB13CWfA@mail.gmail.com>
 <CAEKnhAEmDB6fq7wFs=q965ZmzP-r7mRuOHM1F5DG4-OAsTjNhg@mail.gmail.com>
 <46b289c4-9255-ad66-3410-46b19fc91bf6@gmail.com> <CAFv4g+EPjGd06wnQ448UxL28FnwRGR9Ybf0fJYhpBH-EZfEhxA@mail.gmail.com>
 <8430c6b6-7392-dc74-da19-e4e447fb25db@gmail.com>
In-Reply-To: <8430c6b6-7392-dc74-da19-e4e447fb25db@gmail.com>
Date: Tue, 1 Nov 2022 11:21:56 +0000
Message-ID: <CAFv4g+G-wm+XLLqdbpb36SBn3NJcA7s7mCi9n66Qou_1rmd6fg@mail.gmail.com>
To: Rowan Tommins <rowan.collins@gmail.com>
Cc: internals@lists.php.net
Content-Type: multipart/alternative; boundary="0000000000004933d505ec66efd9"
Subject: Re: [PHP-DEV] Microseconds to error log
From: craig@craigfrancis.co.uk (Craig Francis)

--0000000000004933d505ec66efd9
Content-Type: text/plain; charset="UTF-8"

On Mon, 31 Oct 2022 at 18:23, Rowan Tommins <rowan.collins@gmail.com> wrote:

> I guess we could have the setting be "use new date format", and control
> both the precision and whether the format is ISO 8601 compliant, but I'm
> not convinced of the value
>


Thanks, and that's fair to avoid complicating the error handling routines.

It's not the end of the world to grep for "2022-11-01" in the other logs,
then have to change it to "01-Nov-2022" for the PHP error logs... and yes,
I know, those logs should be empty, but it's not my code, and there's a few
million "Passing null to parameter" errors to ignore ;-)

Craig

--0000000000004933d505ec66efd9--