Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:120516
MIME-Version: 1.0
References: <CAPTD5yHUdoqZ8AA5LzkHY784W2L3mHj2yrazWrGzha7xZ101NQ@mail.gmail.com>
 <25c841b2-d179-ba8d-d452-d0cdd28363d8@php.net> <CAJmy8YHNFv53S6OnA3_Fd3uN+_y_C1rHw7SOnwpaaQ4CnsMjMQ@mail.gmail.com>
In-Reply-To: <CAJmy8YHNFv53S6OnA3_Fd3uN+_y_C1rHw7SOnwpaaQ4CnsMjMQ@mail.gmail.com>
Date: Sat, 3 Jun 2023 00:28:29 +0200
Message-ID: <CAPTD5yHP=cktJ6D4SACz1Gs+eB9xvDGctQspoef6UshM33L9Og@mail.gmail.com>
To: Hans Henrik Bergan <divinity76@gmail.com>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="000000000000347ff105fd2d1348"
Subject: Re: [PHP-DEV] Deprecation of the formats DATE_ISO8601 and DATE_RFC7231
From: jorg.sowa@gmail.com (Jorg Sowa)

--000000000000347ff105fd2d1348
Content-Type: text/plain; charset="UTF-8"

> In my opinion, since it isn't, and likely never was, a legal ISO8601
> string, it's a no-brainer that it should be deprecated. (it's at least
> been illegal since iso8601:2004 released in 2004)

I thought the same when I started the discussion. It's not good promotion
for PHP, when every mention about using proper ISO8601 format starts with
warning (use DATE_ATOM, not ISO_8601!). It doesn't need to be removed
straight in PHP 9. We can wait for next major version.

I just don't understand why keeping invalid concept in the language is
important for such simple structure like constant. I understand it's BC,
but it cannot be keep forever.

I would write RFC anyway to check the reception, but I need Karma to do it.
Could I ask someone for it?

--000000000000347ff105fd2d1348--