Parse DBIx::QuickORM socket DSL keyword instead of core builtin

Open
#2,127 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
53/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Active
Tech stack
java, perl
Domain
compilers

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

area:database area:parser bug

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

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fglock/PerlOnJava

All issues in fglock/PerlOnJava

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.