Support B::Hooks::OP::Check method syntax for Data::Page::Pagination
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 35/100
Rechercherichtung
Start with dev/modules/devel_declare.md and related parser work in #1292 to understand the documented limitation and proposed parser keyword-plugin API. Then trace how Syntax::Feature::Method uses B::Hooks::OP::Check and reproduce the failure with Data::Page::Pagination 0.006 on PerlOnJava. Done means method declarations load and the upstream tests pass on both JVM and interpreter backends, with focused regression coverage for declarations and constructor type checks.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
Data::Page::Pagination 0.006 fails its upstream tests under PerlOnJava because its syntax qw(method) feature cannot load the native B::Hooks::OP::Check dependency. B::Hooks::OP::Check has XS code but no Java XS implementation, and its load fails with no Java XS implementation available.
Evidence
CPAN random tester run 20261117-153921-75160:
- System Perl 5.42.2:
Data-Page-Pagination-0.006passed all 18 tests across 7 test programs. The normal optional skips remained skipped. - PerlOnJava: 3 of the 5 executed subtests failed in
t/01_basics.t; the program exited 255 after four tests. The failing checks wereuse Data::Page::Paginationand the two expected constructor type-constraint errors. - The first failure is explicit:
Can't load loadable object for module B::Hooks::OP::Check: no Java XS implementation available, while loadingsyntaxfromSyntax-Feature-Method. - Later constructor errors report
Found unknown attribute(s) init_arg passed to the constructor: page page_numbers. These are downstream of the failed compile-timemethodfeature and should be rechecked once that feature loads correctly.
The same archived run's system-Perl oracle passed the target distribution's complete suite. This is a PerlOnJava compatibility failure, not an upstream test failure or missing environment prerequisite.
Root cause and scope
Data::Page::Pagination declares methods with method and imports them through use syntax qw(method). That syntax feature depends on parser hooks supplied by B::Hooks::OP::Check (through the Devel::Declare-based method feature). The CPAN install can copy the XS module's Perl files, but PerlOnJava cannot load the native hook because there is no Java implementation. As a result, the package's compile-time declarations are not installed, and module loading and subsequent object construction fail.
The existing design note dev/modules/devel_declare.md records that B::Hooks::OP::Check is pure XS and that parser hook support is not implemented. This issue should establish the minimum compatible path for B::Hooks::OP::Check and the parser/declarator behavior needed by Syntax::Feature::Method, then use this distribution as integration coverage. A Java shim that only makes use B::Hooks::OP::Check succeed is insufficient if it does not implement the compile-time declaration behavior.
Reverse dependencies
MetaCPAN's reverse_dependencies/module/B::Hooks::OP::Check endpoint returned 19 records. Filtering to released distributions with a runtime / requires dependency yields 18 unique distributions; 0 were released in the five years before 2026-11-17. Examples include Devel-Declare, B-Hooks-OP-Check-EntersubForCV, B-Hooks-OP-Check-LeaveEval, B-Hooks-Parser, TryCatch, signatures, multidimensional, and Unicode-Casing. This count indicates a modest but concrete downstream surface; the method-syntax integration failure is independently confirmed by the passing system-Perl oracle and PerlOnJava log.
Acceptance criteria
- Provide Java-backed support sufficient for
B::Hooks::OP::Checkconsumers to load and register the needed compile-time method declarator behavior, or implement an equivalent parser-integrated compatibility path. Syntax::Feature::MethodandData::Page::Pagination0.006 load and pass their upstream tests on PerlOnJava.- Preserve system-Perl behavior and validate the supported path on both JVM and interpreter backends.
- Add focused project-owned regression coverage for the method declaration behavior and the constructor/type-check cases above.
Related broader parser work: #1292, “Design a parser keyword-plugin API for PerlOnJava”. The existing design note is dev/modules/devel_declare.md.
- Vorherrschende Sprache
- Perl
- Sterne
- 67
- Forks
- 8
- Ø Merge
- 5 Std. 12 Min.
- Gemergte PRs (30 T.)
- 131
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus fglock/PerlOnJava
-
area:cpan-port bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
fglock/PerlOnJava#2153 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port area:parser bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
fglock/PerlOnJava#2137 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:backend area:cpan-port area:runtime bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
fglock/PerlOnJava#2071 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:runtime documentation enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
fglock/PerlOnJava#1579 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 62/100
fglock/PerlOnJava#2157 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in fglock/PerlOnJava
Ähnliche Issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOffenteam-cli
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 93/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
inverse-inc/packetfence#9728 ·
Maintainer antworten meist innerhalb von 1 Tag
-
fix(char-create): show the real reason a character is refusedEvtl. vergeben @baphomello hat das vor 1 Tag übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag