Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:114943 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 69986 invoked from network); 18 Jun 2021 09:53:07 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Jun 2021 09:53:07 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id 0AE731804C0 for ; Fri, 18 Jun 2021 03:10:21 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: X-Spam-Status: No, score=-1.5 required=5.0 tests=BAYES_00,KHOP_HELO_FCRDNS, SPF_HELO_NONE,SPF_NONE,UNPARSEABLE_RELAY autolearn=no autolearn_force=no version=3.4.2 X-Spam-Virus: No X-Envelope-From: Received: from processus.org (ns366368.ip-94-23-14.eu [94.23.14.201]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits)) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Fri, 18 Jun 2021 03:10:20 -0700 (PDT) Received: from authenticated-user (PRIMARY_HOSTNAME [PUBLIC_IP]) by processus.org (Postfix) with ESMTPA id 912585101324 for ; Fri, 18 Jun 2021 10:10:19 +0000 (UTC) To: internals@lists.php.net References: Message-ID: Date: Fri, 18 Jun 2021 12:10:19 +0200 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US Authentication-Results: processus.org; auth=pass smtp.auth=pierre-php@processus.org smtp.mailfrom=pierre-php@processus.org X-Spamd-Bar: / Subject: Re: [PHP-DEV] Re: [RFC] is_literal From: pierre-php@processus.org (Pierre) Le 18/06/2021 à 08:00, Craig Francis a écrit : > As there’s been no issues raised with supporting integers, and doing so > will help adoption, the implementation will be updated to allow them. > > Now to choose the name, with the options is_known() from Joe and > is_trusted() from Moritz: > > https://strawpoll.com/bd2qed2xs > > Keep in mind it might also become a dedicated type in the future. > > Craig If I'm understanding this correctly, what you call a literal value is a statically written and compiled string, which doesn't originate from a user given value, but was hardcoded at some point. If so, even if the primary use is of course for security concerns, the realty of what it does is not, it's mostly about how a certain variable was defined / assigned. How about is_static() or is_value_static() ? Or even is_statically_defined() ? There's many options in this path. Regards, -- Pierre