Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

token_get_all(TOKEN_PARSE): class constant named with a reserved keyword is no longer retagged to T_STRING when the same keyword appears in its initializer (regression in 8.3)

未關閉
#23,552 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

@iliaal 已經在處理了。

開始於 2026年9月8日。

  • #23618 來自 @iliaal —— 未關閉

評估

難度
4/5
預估耗時
3-5 天
新手友好度
55/100
Issue 類型
缺陷
描述清晰度
描述清楚
活躍度
活躍
技術堆疊
c, php
領域
compilers

研究方向

從 ext/tokenizer/tokenizer.c 開始,特別查看 ON_FEEDBACK 的處理以及 extract_token_id_to_replace() 路徑,接著重現 issue 中的 token_get_all($code, TOKEN_PARSE) 範例。比較 PHP 8.2 與 PHP 8.3+ 中 class Foo { public const NEW = Bar::NEW; } 的 token 序列。完成標準是宣告和初始化子中的兩處出現都產生 T_STRING,同時不使其他觸發器案例發生回歸。

由索引模型根據 Issue 內容生成。

描述

Bug Extension: tokenizer Status: Verified
Description

Description

Since PHP 8.3, token_get_all($code, TOKEN_PARSE) fails to retag a reserved
keyword used as a class constant name to T_STRING when the same keyword
also appears as a class-constant fetch inside the initializer
of that constant.

The code itself parses, lints and runs fine — only the tokenizer output is wrong.

<?php
$code = '<?php class Foo { public const NEW = Bar::NEW; }';

foreach (token_get_all($code, TOKEN_PARSE) as $t) {
    if (is_array($t) && strcasecmp($t[1], 'new') === 0) {
        echo token_name($t[0]), ' [', $t[1], ']', PHP_EOL;
    }
}

Resulted in this output (PHP 8.3, 8.4, 8.5):

T_NEW [NEW]        <-- declaration: NOT retagged (bug)
T_STRING [NEW]     <-- usage after :: : retagged correctly

But I expected this output instead (and this is what PHP <= 8.2 produces):

T_STRING [NEW]
T_STRING [NEW]

https://3v4l.org/r4Yni — shows the regression starts exactly at 8.3.0 (all 8.2.x
produce the expected output; 8.3.0 through 8.5.10 produce the wrong one).

Trigger conditions

The retagging only fails when the same reserved word occurs both as the
declared constant name and as a :: constant fetch in the initializer:

Code Declared name token on 8.3+
class F { const NEW = 1; } T_STRING ✅
class F { const NEW = Bar::BAZ; } T_STRING ✅
class F { const FOO = Bar::NEW; } (usage) T_STRING ✅
class F { const NEW = Bar::NEW; } T_NEW ❌
class F { const NEW = [self::NEW]; } T_NEW ❌

Reproduced with other semi-reserved keywords as well (the issue is not specific
to new).

Suspected cause

ext/tokenizer/tokenizer.c handles the parser feedback for
"keyword used as identifier" by searching the already-collected token list
backwards by token text and retagging the first match:

case ON_FEEDBACK: {
    HashTable *tokens_ht = ctx->tokens;
    zval *token_zv, *id_zv = NULL;
    ZEND_HASH_REVERSE_FOREACH_VAL(tokens_ht, token_zv) {
        id_zv = extract_token_id_to_replace(token_zv, text, length);
        if (id_zv) {
            break;
        }
    } ZEND_HASH_FOREACH_END();
    ...

Up to PHP 8.2 the class-constant name was reduced (and the feedback emitted)
before the initializer was scanned, so the reverse-by-text search found the
correct token. With typed class constants (PHP 8.3, #10444) the grammar has
to disambiguate the type from the constant name, the reduction of the name
happens later, and by the time the feedback fires the initializer tokens have
already been scanned — so the reverse search finds the initializer occurrence
of the same text instead of the declaration, leaving the declared name tagged
as a keyword.

PHP Version

  • PHP 8.2.33 — not affected (expected output)
  • PHP 8.3 (php:8.3-cli) — affected
  • PHP 8.4 (php:8.4-cli) — affected
  • PHP 8.5.10 (php:8.5-cli) — affected

Operating System

Reproduced on Debian-based official Docker images — the behaviour is platform
independent.

PHP Version
PHP 8.5.9 (cli) (built: Jul 28 2026 13:06:52) (NTS)
Copyright (c) The PHP Group
Built by Homebrew
Zend Engine v4.5.9, Copyright (c) Zend Technologies
    with Zend OPcache v8.5.9, Copyright (c), by Zend Technologies
Operating System

No response

主要語言
C
星號
40.4k
分支
8.2k
平均合併
2 天 17 小時
30 天內合併 PR
115

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

php/php-src 的其他 Issue

查看 php/php-src 的全部 Issue

相似的 Issue

更多 C Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。