Port Math::Random::MT as a bundled Java XS implementation

Ouverte
#2,005 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é
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
45/100
Type d'issue
Fonctionnalité
Clarté
Clairement spécifiée
Activité
Active
Stack technique
java, perl
Domaine
backend, devtools

Piste de recherche

Start by inspecting the bundled Java XS bridge pattern and registry, then read the upstream Math-Random-MT 1.17 tests and implementation to identify the required seeded vectors and API behavior. Add the bridge, Perl shim, and focused project tests; validate those tests with system Perl first. Done means the upstream suite and both named Games-Solitaire-BlackHole-Solver tests pass on JVM and interpreter backends, with no runtime need for MT.xs or _mt.c.

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

Description

area:cpan-port enhancement

Summary

Add a bundled Java implementation of Math::Random::MT so PerlOnJava can load the CPAN module without its XS binary. This should also unblock CPAN consumers that require Math::Random::MT at runtime, including Games-Solitaire-BlackHole-Solver.

Evidence

CPAN random run 20261109-091152-39587 tested Games-Solitaire-BlackHole-Solver 0.18.0. Under PerlOnJava, t/00-compile.t could not load Math::Random::MT because no Java XS implementation was available; t/01-run.t then failed after the solver could not run. The system-Perl oracle passed the complete target suite: 27/27 tests across both test programs. The same system-Perl run built and passed Math-Random-MT 1.17's nine test files (125 tests).

The failed solver requires Math::Random::MT at runtime. Targeted MetaCPAN reverse-dependency data reports 13 unique released CPAN distributions with runtime dependencies, 4 recent; examples include Games-Solitaire-BlackHole-Solver, Task-BeLike-SHLOMIF, Log-GELF-Util, and Bencher-Scenario-RandomNumbers.

Proposed implementation

Provide the Java XS bridge and Perl shim for the Math::Random::MT API, following the project's existing Java XS bridge pattern. Bouncy Castle is already a project dependency, but its documented RandomGenerator is an interface and does not itself provide an MT19937 engine. Avoid assuming that a Bouncy Castle DRBG has MT19937-compatible sequences. A small pure-Java MT19937 implementation avoids adding another runtime dependency; Apache Commons RNG is an alternative only if its additional dependency and seed/output compatibility are justified.

Preserve the CPAN module's behavior and seeded sequence, including:

  • Object interface: new, set_seed, get_seed, rand, and irand.
  • Functional interface and optional exports: srand, rand, and irand.
  • Single unsigned 32-bit seed and array seeding (up to 624 words), including the published high-value seed cases.
  • Automatic seeding when no seed is supplied, without changing Perl's CORE::rand state beyond the upstream behavior.
  • Unsigned 32-bit results from irand and [0, n) floating-point results from rand(n).

Acceptance criteria

  • Add the module to the bundled Java XS registry and provide the required Perl-facing shim, without modifying upstream CPAN tests.
  • Add project-owned focused tests for seeded MT19937 output, array seeding, unsigned output, OO calls, function imports, and automatic seeding. Validate new Perl unit tests with system Perl first as required by the repository.
  • Run the upstream Math-Random-MT 1.17 suite with the Java implementation and confirm its deterministic vectors match system Perl.
  • Re-run Games-Solitaire-BlackHole-Solver 0.18.0 with PerlOnJava and confirm both t/00-compile.t and t/01-run.t pass; test JVM and interpreter backends.
  • Confirm native MT.xs/_mt.c is not needed at runtime when the Java implementation is selected.

References

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.