Support B::Hooks::OP::Check method syntax for Data::Page::Pagination
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 35/100
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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.
- Lingua principale
- Perl
- Stelle
- 67
- Fork
- 8
- Merge medio
- 5h 12m
- PR unite (30g)
- 131
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fglock/PerlOnJava
-
area:cpan-port bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
fglock/PerlOnJava#2153 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port area:parser bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 68/100
fglock/PerlOnJava#2137 ·
I maintainer di solito rispondono entro 1 giorno
-
area:backend area:cpan-port area:runtime bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
fglock/PerlOnJava#2071 ·
I maintainer di solito rispondono entro 1 giorno
-
area:runtime documentation enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
fglock/PerlOnJava#1579 ·
I maintainer di solito rispondono entro 1 giorno
-
area:cpan-port bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 62/100
fglock/PerlOnJava#2157 ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di fglock/PerlOnJava
Issue simili
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksApertateam-cli
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 93/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
inverse-inc/packetfence#9728 ·
I maintainer di solito rispondono entro 1 giorno
-
fix(char-create): show the real reason a character is refusedForse già presa @baphomello l’ha presa 1 giorno fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
I maintainer di solito rispondono entro 1 giorno