Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

PadWalker peek_our misses file-scope our variables on JVM

Abierto
  • ¿Algo no está bien?
#1,669 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
57/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, perl
Área
backend, testing

Línea de trabajo

Start with the existing PadWalker regression coverage for peek_our(0) inside a subroutine and trace how the JVM backend handles that lookup; the issue does not name the relevant files. Add project-owned top-level coverage for both JVM and interpreter backends, checking the expected variable names and references against system Perl. Run the regression tests and the Test::Expander upstream suite; done means the exports load and the suite proceeds.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

area:backend bug

Summary

After adding the bundled Scalar::Readonly support for #1664, jcpan -t Test::Expander 2.7.1 gets past the missing XS implementation but all 26 test programs fail while loading Test::Expander::Constants. The module populates @EXPORT_OK from PadWalker::peek_our(0) at file scope; on the JVM that lookup does not return its package variables, so imports such as $COMMENT, %OPTION_PARSER, and %REST_CONSTANTS_TO_EXPORT are reported as not exported.

Reproduction

use PadWalker qw(peek_our);
our $probe = 17;
my $vars = peek_our(0);
print join(',', sort keys %$vars), "\n";

System Perl reports $probe; PerlOnJava's JVM reports an empty key list. The existing PadWalker regression covers peek_our(0) inside a subroutine, but not at file scope.

The affected upstream run used nice -n 19 timeout 1800 ./jcpan -t Test::Expander. It failed 26/26 programs before their tests could run, with “is not exported by Test::Expander::Constants” errors. This is a follow-up to #1664: the missing Scalar::Readonly XS support is now available, and this issue tracks the separate PadWalker::peek_our behavior needed by this consumer.

Expected behavior

PadWalker::peek_our(0) should expose package our variables at file scope with Perl-compatible names and references, so Test::Expander::Constants can build its export list and the upstream suite can proceed.

Regression coverage

Add project-owned coverage for top-level peek_our(0) on both JVM and interpreter backends, validate the oracle with system Perl, then rerun the Test::Expander upstream suite.

Lenguaje dominante
Perl
Estrellas
64
Forks
7
Merge medio
5 h 25 min
PR fusionados (30 d)
178

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de fglock/PerlOnJava

Todos los issues de fglock/PerlOnJava

Issues similares

Más issues de Perl

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.