Nested require loses package for helper subs in List::Vectorize

Offen
#2,078 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
52/100
Issue-Typ
Bug
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
java, perl
Bereich
backend

Rechercherichtung

Start by comparing this nested dependency load with the caller/package handling and regression coverage added for #1601. Reproduce with ./jcpan -t Statistics::Multtest, then run the focused ./jperl command from the issue on both JVM and interpreter backends. Add a project owned regression test for the minimal nested load, and confirm the reproducer and all 52 unchanged Statistics-Multtest assertions pass.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:cpan-port area:runtime bug

Summary

Statistics::Multtest 0.14 fails six assertions in t/1prototype.t on the PerlOnJava JVM backend. Its initial routine calls List::Vectorize::is_array_ref and List::Vectorize::is_hash_ref, but those functions are not present in the expected package after use Statistics::Multtest loads List::Vectorize and its helper files.

The same distribution and dependencies pass under system Perl. This appears related to package context while loading a nested required Perl file without an explicit package declaration, and may be a remaining case in the nested-require caller/package handling addressed by #1601. The small reproducer below fails in the current checkout.

Reproduction

Install Statistics::Multtest 0.14 and its List::Vectorize dependency, then load them through the distribution's normal module path:

./jcpan -t Statistics::Multtest

The failing calls can be isolated after the distributions are installed:

./jperl \
  -I<Statistics-Multtest-blib-lib> \
  -I<List-Vectorize-blib-lib> \
  -e 'use Statistics::Multtest; Statistics::Multtest::initial([0.1])'

On the JVM backend this dies with:

Undefined subroutine &List::Vectorize::is_array_ref called

In List::Vectorize 1.05, is_array_ref is defined in List/Vectorize/lib/Datatype.pl. That file has no package declaration; it is loaded by List::Vectorize.pm using require. With List::Vectorize loaded directly in a top-level one-liner, the symbol is present, but when loaded as a dependency of Statistics::Multtest, it is absent from List::Vectorize's package.

Evidence

  • Distribution/version: Statistics-Multtest 0.14; dependency List-Vectorize 1.05.
  • Archived CPAN run: 20261117-092012-89323.
  • PerlOnJava JVM backend: 46/52 assertions passed; six failures (tests 1, 3, 5, 7, 9, and 11) in t/1prototype.t, all failing at the undefined List::Vectorize::is_array_ref call in Statistics::Multtest::initial.
  • System Perl oracle from the same run: Statistics-Multtest passed all 52 tests; List-Vectorize passed all 643 dependency tests.
  • No XS/native dependency is involved.
  • The isolated reproducer was run on the JVM backend. Interpreter behavior has not yet been checked.

Expected behavior

Loading List::Vectorize as a dependency should define its helper functions in List::Vectorize, so Statistics::Multtest::initial can validate array and hash references as it does under system Perl.

Related issue

This may be an additional package-context case related to #1601 (nested require caller context). The focused Statistics::Multtest reproducer above still fails in the current checkout and should be compared against the regression coverage added for that issue.

Acceptance criteria

  • Add a project-owned regression test for the minimal nested dependency load and validate its expected behavior under system Perl.
  • Make the focused reproducer pass on both JVM and interpreter backends.
  • Rerun the unchanged Statistics-Multtest 0.14 test suite and confirm all 52 assertions pass.
Vorherrschende Sprache
Perl
Sterne
67
Forks
8
Ø Merge
5 Std. 12 Min.
Gemergte PRs (30 T.)
131

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fglock/PerlOnJava

Alle Issues in fglock/PerlOnJava

Ähnliche Issues

Weitere Issues zu Perl

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.