Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115042
Date: Tue, 22 Jun 2021 20:50:45 +0100
User-Agent: K-9 Mail for Android
In-Reply-To: <CAFv4g+Gv1qQ2Gtx2Qwo0Dx2Cb_gOXJ=rm7rVy+Jo89PmD-3jnA@mail.gmail.com>
References: <CAFv4g+Gv1qQ2Gtx2Qwo0Dx2Cb_gOXJ=rm7rVy+Jo89PmD-3jnA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable
To: internals@lists.php.net,Craig Francis <craig@craigfrancis.co.uk>,PHP internals <internals@lists.php.net>
Message-ID: <60ACEB8C-43F7-4ED4-8365-01AC9F6CB544@php.net>
Subject: Re: [PHP-DEV] [RFC] Name issue - is_literal/is_trusted
From: derick@php.net (Derick Rethans)

On 22 June 2021 19:11:05 BST, Craig Francis <craig@craigfrancis=2Eco=2Euk> =
wrote:
>Hi Internals,
>
>As the name `is_trusted()` seems to be causing contention, I think more
>than the alternative option would=2E Since we want to get this right, and
>we
>still have time before the feature freeze, this might be worth
>re-looking
>at=2E Particularly if you are one of those unsure about it, read on=2E

Just changing the name to something not misleading isn't going to change m=
y opinion about voting for this=2E It's grown into a concoction of differen=
t things than the original is_literal, that just checks a single string for=
 its literalness=2E=20

cheers,=20
Derick=20