Re: [RFC] [VOTE] is_literal
| From: | Lauri Kenttä | Date: | Fri, 09 Jul 2021 10:49:50 +0000 |
| Subject: | Re: [RFC] [VOTE] is_literal | ||
| References: | 1 2 | Groups: | php.internals |
| Request: | Send a blank email to internals+get-115378@lists.php.net to get a copy of this message | ||
On 2021-07-07 12:23, Nikita Popov wrote:
permanent interned strings, which will be predominantly (or entirely?) non-literal. At least it doesn't look to me like names of internal functions/classes/etc are considered literal. I think this may be problematic, in that now the permanent non-literal interned string in the function/class tables will be different from the per-request literal interned string used by user code to reference it.Just wondering, if this is a major performance problem, is there a compelling reason why the internal names couldn't be marked literal (even if it's technically "wrong")? It seems unlikely to get a function or class name accidentally in a SQL query and even less likely that user input was involved. -- Lauri Kenttä