Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120366
MIME-Version: 1.0
References: <CAPTD5yHUdoqZ8AA5LzkHY784W2L3mHj2yrazWrGzha7xZ101NQ@mail.gmail.com>
 <ada65004-742f-4d21-96f7-e6c3b21e7f80@app.fastmail.com>
In-Reply-To: <ada65004-742f-4d21-96f7-e6c3b21e7f80@app.fastmail.com>
Date: Fri, 19 May 2023 23:16:40 +0200
Message-ID: <CAPTD5yE8z75DPpL_5NJ1n_KvGxmr_m-xyekqvntv-2+twYaLpw@mail.gmail.com>
To: Larry Garfield <larry@garfieldtech.com>
Cc: php internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="00000000000099694e05fc1270da"
Subject: Re: [PHP-DEV] Deprecation of the formats DATE_ISO8601 and DATE_RFC7231
From: jorg.sowa@gmail.com (Jorg Sowa)

--00000000000099694e05fc1270da
Content-Type: text/plain; charset="UTF-8"

> How common is it in the wild?  I am pretty sure I've used it myself
without really thinking many times, which I suspect is common.  Knowing how
much code would be impacted would determine how we'd go about deprecating
it and on what timeline.

I'm not sure how would be possible to find out. I suppose most of the
frameworks (and thus popular PHP libraries) avoid this constant as showed
in Drupal and Carbon. The scanning of popular libraries will not show the
scale of the problem (however I will do it tomorrow) Helpful fact is that
those constants are just constants so it's easily replaceable with
strings 'Y-m-d\\TH:i:sO'
and 'D, d M Y H:i:s \\G\\M\\T'.

--00000000000099694e05fc1270da--