Parse DBIx::QuickORM socket DSL keyword instead of core builtin
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 53/100
Research direction
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.
Written by the indexing model from the issue text.
Description
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
- Dominant language
- Perl
- Stars
- 67
- Forks
- 8
- Avg merge
- 5h 12m
- Merged PRs (30d)
- 131
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from fglock/PerlOnJava
-
area:cpan-port bug
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
fglock/PerlOnJava#2153 ·
Maintainers usually reply within 1 day
-
area:cpan-port area:parser bug
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fglock/PerlOnJava#2137 ·
Maintainers usually reply within 1 day
-
area:backend area:cpan-port area:runtime bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
fglock/PerlOnJava#2071 ·
Maintainers usually reply within 1 day
-
area:runtime documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
fglock/PerlOnJava#1579 ·
Maintainers usually reply within 1 day
-
area:cpan-port bug
Difficulty 3/5 1-2 days Newbie friendliness 62/100
fglock/PerlOnJava#2157 ·
Maintainers usually reply within 1 day
All issues in fglock/PerlOnJava
Similar issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOpenteam-cli
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
Difficulty 1/5 Under an hour Newbie friendliness 93/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
inverse-inc/packetfence#9728 ·
Maintainers usually reply within 1 day
-
fix(char-create): show the real reason a character is refusedPossibly taken @baphomello claimed this 1 day ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day