Port autovivification pragma to PerlOnJava

Open
#2,083 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
java, perl
Domain
backend

Research direction

Start by reading the autovivification 0.18 import/unimport documentation and the PerlOnJava compiler/runtime paths that handle lexical pragmas on both backends. Then review issues #1958 and #1980 for related core behavior. Done means both backends load the pragma without XS errors, focused tests cover its categories and nested scopes, and Data-Session 1.18's upstream tests pass.

Written by the indexing model from the issue text.

Description

area:cpan-port enhancement

Summary

Port the CPAN autovivification pragma to PerlOnJava so modules that declare use autovivification or no autovivification can load and receive the pragma's documented lexical behavior without relying on XS.

Evidence

The PerlOnJava CPAN run 20261117-153921-75160 tested Data-Session 1.18. Its system-Perl oracle passed all 3 test programs (52 tests). The PerlOnJava run failed all 3 programs before any subtests ran because the dependency autovivification 0.18 calls XSLoader::load; PerlOnJava reported that no Java XS implementation is available. Data::Session and its tests use the pragma lexically, including no autovivification in library files.

autovivification contains XS/C code and cannot currently be loaded by PerlOnJava. A targeted released dependency lookup found 39 unique distributions with a required runtime dependency, 20 of them released in the last five years. Representative dependants include JSON-Schema-Modern, App-Netdisco, OpenAPI-Modern, Spreadsheet-Edit, Test-JSON-Schema-Acceptance, and Mojolicious-Plugin-OpenAPI-Modern.

This request is for a PerlOnJava implementation of the pragma's behavior, not support for compiling arbitrary XS modules.

Porting scope

Implement a Java-backed replacement compatible with autovivification 0.18's documented import/unimport interface and lexical scope. Cover the categories fetch, exists, delete, and store, plus warn and strict modes and their category arguments. Preserve the module's documented default categories and behavior when nested scopes enable or disable the pragma. Determine the right compiler/runtime hook for this lexical behavior and make it work consistently on both JVM and interpreter backends.

The implementation should allow the upstream pure-Perl module entry point to load without attempting to load the XS object when PerlOnJava provides the implementation. Keep standard Perl behavior unchanged.

Acceptance criteria

  • use autovivification and no autovivification load on both PerlOnJava backends without XS load errors.
  • Focused tests cover lexical enable/disable scope and each documented behavior category, including warning/strict modes.
  • The tests pass under system Perl and both PerlOnJava backends.
  • Data-Session 1.18's upstream tests pass under PerlOnJava with the pragma available.
  • Add permanent project-owned regression coverage for the implemented pragma behavior.

Related issues

Issues #1958 and #1980 address specific core autovivification behaviors. They do not provide the lexical pragma or its category controls.

Dominant language
Perl
Stars
67
Forks
8
Avg merge
5h 12m
Merged PRs (30d)
131

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fglock/PerlOnJava

All issues in fglock/PerlOnJava

Similar issues

More Perl issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.