Support B::Hooks::OP::Check method syntax for Data::Page::Pagination
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 5/5
- 見積もり時間
- 1週間以上
- 初心者へのやさしさ
- 35/100
調査の方向性
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.
索引モデルが issue の本文から書いたものです。
説明
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.
- 主要言語
- Perl
- スター
- 67
- フォーク
- 8
- 平均マージ
- 5時間 12分
- マージ済み PR(30日)
- 131
環境構築
- Dockerfile または Docker Compose ファイルあり
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- 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 日以内に返信