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

caller reports void context for scalar eval caller frame

Cerrado
  • ¿Algo no está bien?
#1,859 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
48/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
java, perl
Área
backend, testing

Línea de trabajo

Start with the caller-frame context tracking path used by caller(1)[5] and the existing upstream regression test t/002_must_be_list.t. Reproduce the scalar and void eval cases on both JVM and interpreter backends, then trace how each backend reports the caller context. Done means the project-owned regression coverage passes with system Perl and the upstream suite passes on both PerlOnJava backends.

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

Descripción

area:runtime bug

Summary

caller(1)[5] reports void instead of scalar for the caller frame when a failing call is made through a scalar eval.

Reproducer

Call Call::Context::must_be_list() from foo, where try_it returns foo(), then run:

eval { try_it() };
scalar eval { try_it() };
scalar eval { () = try_it() };

The upstream Call-Context 0.05 test t/002_must_be_list.t expects the second call's exception to identify scalar context and the third call to succeed.

Evidence

  • PerlOnJava b8e16493d, JVM backend, Java 24.0.2, macOS arm64: 1/6 assertions failed in t/002_must_be_list.t; actual diagnostic says foo called in non-list (void) context during the scalar eval.
  • Interpreter backend on the same checkout also reports void for the scalar case and has an additional failure in the list case.
  • System Perl 5.42.2 passes all 6 assertions; the archived CPAN oracle for run 20261021-223510-14962 passes all 13 tests across all three test files.
  • The same CPAN run records the PerlOnJava failure as 12/13 tests, with test 5 failing in t/002_must_be_list.t.
  • The archived regression record identifies d5170d2d0 as the last-known-working version.

The distribution is pure Perl. This appears to be a PerlOnJava caller-frame context tracking issue; the JVM and interpreter backends are both affected.

Acceptance criteria

  • caller(1)[5] reports scalar for the scalar-eval call and undef for the void call.
  • The upstream Call-Context 0.05 test suite passes on both PerlOnJava backends.
  • Add permanent project-owned regression coverage and validate it with system Perl.
Lenguaje dominante
Perl
Estrellas
64
Forks
8
Merge medio
5 h 42 min
PR fusionados (30 d)
205

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.