Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:102586
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.214.52 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CAF+90c8kdruJHDu9tXSOrc6L+v8-nQ1x1UjD4dqPiWP9eCvQ1Q@mail.gmail.com>
References: <CAF+90c8kdruJHDu9tXSOrc6L+v8-nQ1x1UjD4dqPiWP9eCvQ1Q@mail.gmail.com>
Date: Wed, 4 Jul 2018 22:36:08 +0200
Message-ID: <CAF+90c-Nfq8rY0Kun8ye0EitXdoUzvVwP=PXLJaSLfOhX+a9mA@mail.gmail.com>
To: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000007795ea057032612d"
Subject: Re: [RFC] Deprecate and remove case-insensitive constants
From: nikita.ppv@gmail.com (Nikita Popov)

--0000000000007795ea057032612d
Content-Type: text/plain; charset="UTF-8"

On Sun, Jun 24, 2018 at 1:18 PM, Nikita Popov <nikita.ppv@gmail.com> wrote:

> Hi internals,
>
> I'd like to propose the deprecation (in PHP 7.3) and removal (in PHP 8) of
> case-insensitive constants:
>
> https://wiki.php.net/rfc/case_insensitive_constant_deprecation
>
> This was already discussed some time ago on the list, though that
> discussion degenerated into unfortunate directions. I'd very much
> appreciate if we could keep discussions on making PHP fully case-sensitive
> or fully case-insensitive outside of this thread. (Feel free to open a new
> one though.)
>
> The main point I'd like to have feedback on is the handling of true, false
> and null, as I'm not sure what the best approach regarding that is.
>
> Regards,
> Nikita
>

Based on the received feedback, the RFC now specifies that true/false/null
will become reserved keywords rather than special-cased constants in PHP 8.
Should we run into some unexpected BC issues while doing that, we can
reconsider adding some special checks to mitigate impact.

Nikita

--0000000000007795ea057032612d--