Parse DBIx::QuickORM socket DSL keyword instead of core builtin
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
研究方向
Start by tracing how the parser resolves bareword keywords against Perl builtins, using the socket $db->socket; examples and diagnostics from t/aside.t, t/coldconnect.t, and t/forked.t as reproduction points. Find the parser entry point and related tests, then check that this DSL form is accepted without changing how ordinary calls to the core socket builtin are parsed.
由索引模型根據 Issue 內容生成。
描述
Summary
PerlOnJava parses the bareword socket in DBIx::QuickORM's declarative DSL as Perl's core socket builtin. That produces a compile-time prototype error even though this syntax passes under standard Perl.
Reproduction
DBIx::QuickORM 0.000019 includes declarations such as:
if (curdialect() =~ m/MySQL/) {
socket $db->socket;
user $db->username;
pass $db->password;
}
The same form occurs in t/aside.t, t/coldconnect.t, and t/forked.t. In the PerlOnJava CPAN run 20261119-133823-51077, compilation stopped with:
Not enough arguments for socket at t/aside.t line 24, near ";"
Not enough arguments for socket at t/coldconnect.t line 17, near ";"
Not enough arguments for socket at t/forked.t line 19, near ";"
The system-Perl oracle completed the DBIx::QuickORM 0.000019 test suite successfully. PerlOnJava's run failed 26 of 30 test programs (26 subtests were reached; the majority of programs exited before completing their TAP plans).
Expected behavior
Within the DBIx::QuickORM declaration DSL, socket $db->socket; should be parsed as a DSL keyword followed by its argument, consistent with standard Perl and the module's supported syntax.
Likely area
Parser keyword/builtin resolution for bareword DSL keywords. The diagnostic indicates that socket is resolved using the core builtin's prototype, rather than as the DSL term.
Related environment result
This run also failed to build the XS prerequisite UUID 0.40 (make: Generating: No such file or directory). That is a separate native-build limitation and is already tracked by issue #1670, “Port UUID with Java UUID libraries.” It does not account for the socket parser diagnostics.
Evidence
- CPAN random tester run:
20261119-133823-51077 - Distribution: DBIx-QuickORM 0.000019, selected through DBIx::QuickORM::Util::HashBase
- Standard Perl oracle: PASS
- PerlOnJava target: 26/30 test programs failed, with the three parser errors listed above
- 主要語言
- Perl
- 星號
- 67
- 分支
- 8
- 平均合併
- 5 小時 12 分鐘
- 30 天內合併 PR
- 131
環境準備
- 提供 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
fglock/PerlOnJava 的其他 Issue
-
area:cpan-port bug
難度 2/5 1-3 小時 新手友好度 70/100
fglock/PerlOnJava#2153 ·
維護者通常 1 天內回覆
-
area:cpan-port area:parser bug
難度 2/5 1-3 小時 新手友好度 68/100
fglock/PerlOnJava#2137 ·
維護者通常 1 天內回覆
-
area:backend area:cpan-port area:runtime bug
難度 2/5 1-3 小時 新手友好度 76/100
fglock/PerlOnJava#2071 ·
維護者通常 1 天內回覆
-
area:runtime documentation enhancement
難度 2/5 1-3 小時 新手友好度 72/100
fglock/PerlOnJava#1579 ·
維護者通常 1 天內回覆
-
area:cpan-port bug
難度 3/5 1-2 天 新手友好度 62/100
fglock/PerlOnJava#2157 ·
維護者通常 1 天內回覆
查看 fglock/PerlOnJava 的全部 Issue
相似的 Issue
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling links未關閉team-cli
難度 2/5 1-3 小時 新手友好度 70/100
維護者通常 2 天內回覆
-
難度 2/5 1-3 小時 新手友好度 66/100
-
難度 1/5 1 小時以內 新手友好度 93/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 73/100
inverse-inc/packetfence#9728 ·
維護者通常 1 天內回覆
-
fix(char-create): show the real reason a character is refused可能已有人在做 @baphomello 於 1 天前認領。 未關閉
難度 2/5 1-3 小時 新手友好度 84/100
維護者通常 1 天內回覆