Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:115044
MIME-Version: 1.0
References: <CAFv4g+Gv1qQ2Gtx2Qwo0Dx2Cb_gOXJ=rm7rVy+Jo89PmD-3jnA@mail.gmail.com>
 <60ACEB8C-43F7-4ED4-8365-01AC9F6CB544@php.net>
In-Reply-To: <60ACEB8C-43F7-4ED4-8365-01AC9F6CB544@php.net>
Date: Tue, 22 Jun 2021 21:35:04 +0100
Message-ID: <CAGBsUrcf=T_JvwcpfVeVy+nbVfuJn6cWz5MRoCw489X0y0pSNQ@mail.gmail.com>
To: Derick Rethans <derick@php.net>
Cc: Craig Francis <craig@craigfrancis.co.uk>, PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary="0000000000003c763305c560ba75"
Subject: Re: [PHP-DEV] [RFC] Name issue - is_literal/is_trusted
From: tekiela246@gmail.com (Kamil Tekiela)

--0000000000003c763305c560ba75
Content-Type: text/plain; charset="UTF-8"

FWIW, I would prefer is_literal, but without integers in scope. Modern code
is often type hinted. I would expect that a lot of libraries would accept
only strings and then check whether it's a literal string. I don't think
accepting integers in scope increases security or improves ease of use.
However, I am more concerned about other things that have been mentioned in
this thread and the overall disagreement. I'd rather not rush this change.
Also, I am concerned about the performance of applications that are heavy
on string processing. Although I haven't tested this yet myself.

--Kamil

--0000000000003c763305c560ba75--