Stash enumeration omits inherited import after use

Ouverte
#2,136 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
45/100
Type d'issue
Bug
Clarté
Clairement spécifiée
Activité
Active
Stack technique
java, perl
Domaine
compilers

Piste de recherche

Start in HashSpecialVariable.computeStashEntries, the enumeration the report blames for skipping names inherited through @ISA. Reproduce first with the inline snippet against both backends, then mirror the failing assertion from t/02_full_functions.t in a new project-owned regression test and confirm it passes on system Perl before touching the enumeration. Done means the new test and unmodified Module-Functions 2.1.3 pass on JVM and interpreter, with existing stash deletion and freed-namespace tests (#1980/#2028) still green.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:runtime bug

Summary

Module::Functions 2.1.3 fails t/02_full_functions.t on PerlOnJava because get_full_functions('Bar') omits import from keys %Bar::. System Perl passes the complete distribution suite. The same missing stash key reproduces on both PerlOnJava execution backends.

Minimal reproduction

package Bar;
use strict;
use warnings;
use parent qw/Exporter/;
use File::Spec::Functions qw/catfile/;
sub bar { '5963' }

package main;
use Bar;
no strict 'refs';
print join(" ", sort keys %Bar::), "\n";

On system Perl, the package keys include import. On PerlOnJava, the import key is absent. In the upstream test, this makes the actual sorted result lack the final import entry:

[ qw/BEGIN EXPORT _barbar bar catfile import/ ]

The inherited Exporter::import is callable through @ISA; the mismatch is in the package stash enumeration exposed by %Bar::.

Root cause

HashSpecialVariable.computeStashEntries constructs stash keys from PerlOnJava's registered scalar, aggregate, code, IO, and format slots. It includes directly registered package CODE slots, but the inherited import method resolved through Bar's @ISA is not represented in that enumeration. Thus method dispatch succeeds while keys %Bar:: omits a name that system Perl exposes after use Bar resolves the inherited import method.

The fix should make stash enumeration match Perl's visible post-use package stash for inherited methods, while preserving current lookup, deletion, and freed-namespace behavior.

Evidence

  • CPAN distribution: Module-Functions 2.1.3; archived run 20261119-133823-51077.
  • PerlOnJava CPAN result: t/00_compile.t and t/01_simple.t pass; t/02_full_functions.t fails its only assertion because import is absent (5/6 total assertions pass).
  • System Perl 5.42.2 oracle: all 3 test programs and all 6 assertions pass.
  • PerlOnJava JVM backend: the CPAN test fails as above.
  • PerlOnJava interpreter backend: the same t/02_full_functions.t assertion fails with import absent.
  • The distribution is pure Perl and has no native/XS prerequisite. Reproduction environment: macOS arm64, Java 24, PerlOnJava 5.44.1 build f00b834bab.

Acceptance criteria

  • Add a project-owned focused regression for stash enumeration after inherited import resolution; validate it on system Perl first.
  • Pass the focused regression on both JVM and interpreter backends.
  • Pass the unmodified Module-Functions 2.1.3 test suite on PerlOnJava.
  • Preserve existing stash deletion and namespace visibility behavior.

Related but distinct: #1980 / #2028 fixed deleted child namespaces reappearing during stash enumeration. This report concerns omission of an inherited method name after use and is not a duplicate of that issue.

Langage dominant
Perl
Étoiles
67
Forks
8
Merge moyen
5 h 12 min
PR mergées (30 j)
131

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de fglock/PerlOnJava

Toutes les issues de fglock/PerlOnJava

Issues similaires

Plus d'issues Perl

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.