Support CPAN modules requiring Object::Pad 0.800+
Maintainer antworten meist innerhalb von 1 Tag
Dieses Issue hat noch niemand übernommen.
Bewertung
- Schwierigkeit
- 5/5
- Geschätzter Aufwand
- Über eine Woche
- Anfängerfreundlichkeit
- 25/100
Rechercherichtung
Start with the bundled Object::Pad compatibility pragma and native class compiler, then review Device::Chip 0.27's Object::Pad usage and the related architecture issue #1586. Identify the syntax and APIs needed for that consumer and define the supported version boundary with clear failures for unsupported APIs. Add project-owned regression coverage, validate behavior against system Perl and both PerlOnJava backends, and run the unchanged Device-Chip-ADT7470-0.03 suite with its fake adapter.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Beschreibung
Summary
PerlOnJava's bundled Object::Pad compatibility pragma advertises version 0.66 and implements a documented subset of Object::Pad syntax. Current CPAN code can require Object::Pad 0.800 or newer, but installing current Object::Pad on PerlOnJava cannot supply that version: Object::Pad 0.825 depends on XS::Parse::Keyword and XS::Parse::Sublike, which require native XS support that PerlOnJava does not provide. The resulting test failure is a compatibility gap between the bundled syntax implementation and modern CPAN prerequisites.
Evidence: Device::Chip::ADT7470
CPAN random run 20261118-104825-43075 tested Device-Chip-ADT7470-0.03. The test harness built dependency Device-Chip-0.27; its source declares use Object::Pad 0.800. The dependency build found bundled Object::Pad 0.66, then attempted Object::Pad 0.825. Its prerequisite builds could not load XS::Parse::Keyword (no Java XS implementation available), and the PerlOnJava XS fallback could not install a usable Object::Pad implementation.
The target's t/00use.t then failed because it received Object::Pad 0.66 where 0.800 was required. t/01config.t and t/02interact.t stopped at the same version requirement; t/99pod.t passed. Device::Chip::ADT7470 itself is pure Perl, and these adapter tests use a test adapter rather than physical hardware. The archived run records the JVM test path; interpreter and system-Perl outcomes were not established. The host's system Perl did not have Object::Pad installed during investigation, so no standard-Perl comparison is claimed.
This is consistent with the checked-in compatibility layer's declared scope: it reports version 0.66, supports selected native class/field/method syntax, and does not provide Object::Pad MOP or extension APIs. The immediate diagnostic is a version guard, not evidence that the driver module's own code is defective.
Ecosystem scope
A targeted MetaCPAN reverse-dependency lookup, filtered to unique released distributions with a runtime requires dependency on Object::Pad, found 138 distributions, of which 134 were released in the five years through 2026-11-19. Examples include OpenTelemetry, OpenTelemetry-SDK, DBIx-Fast, Getopt-Pad, and Device-Serial-SLuRM. These counts support tracking compatibility for modern consumers; they do not imply that all consumers need MOP or other unsupported APIs.
Requested work
Determine and implement a compatibility path for CPAN modules that declare Object::Pad >= 0.800 and use syntax/features that PerlOnJava can implement natively. Keep the version advertised by the bundled shim honest: do not satisfy the version check unless the required behavior is supported. Identify the syntax/API subset needed by representative consumers, starting with Device::Chip 0.27, and provide clear diagnostics when a required extension still needs XS or an unsupported MOP API.
Related architecture work: #1586 investigates general native XS and Perl C API compatibility. This issue is the bounded Object::Pad compatibility outcome; it does not assume that general XS support is a prerequisite if the needed syntax can be implemented in PerlOnJava's compiler.
Acceptance criteria
- Document the supported Object::Pad version and feature boundary for the chosen implementation.
- Add project-owned regression coverage for the new supported behavior and for a clear failure when a consumer requires an unsupported Object::Pad API.
- Validate new Perl-level behavior against system Perl first, then verify both PerlOnJava backends.
- Run the unchanged
Device-Chip-ADT7470-0.03test suite with its fake adapter and record the system Perl, JVM, and interpreter results. - Preserve the existing unsupported-XS diagnostics for features that cannot be implemented by the native class compiler.
- Vorherrschende Sprache
- Perl
- Sterne
- 67
- Forks
- 8
- Ø Merge
- 5 Std. 12 Min.
- Gemergte PRs (30 T.)
- 131
Entwicklungsumgebung
- Enthält ein Dockerfile oder eine Docker-Compose-Datei
- Keine Pull-Request-Vorlage
- Beitragsleitfaden lesen
Erste Schritte
- Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
- Forken Sie das Repository und arbeiten Sie in einem Branch.
- Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.
Mehr aus fglock/PerlOnJava
-
area:cpan-port bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
fglock/PerlOnJava#2153 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port area:parser bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 68/100
fglock/PerlOnJava#2137 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:backend area:cpan-port area:runtime bug
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 76/100
fglock/PerlOnJava#2071 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:runtime documentation enhancement
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 72/100
fglock/PerlOnJava#1579 ·
Maintainer antworten meist innerhalb von 1 Tag
-
area:cpan-port bug
Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 62/100
fglock/PerlOnJava#2157 ·
Maintainer antworten meist innerhalb von 1 Tag
Alle Issues in fglock/PerlOnJava
Ähnliche Issues
-
Dev-output directory preparation accepts file-valued lib/include paths and fails on dangling linksOffenteam-cli
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 70/100
Maintainer antworten meist innerhalb von 2 Tagen
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 66/100
-
Schwierigkeit 1/5 Unter einer Stunde Anfängerfreundlichkeit 93/100
Maintainer antworten meist innerhalb von 1 Tag
-
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 73/100
inverse-inc/packetfence#9728 ·
Maintainer antworten meist innerhalb von 1 Tag
-
fix(char-create): show the real reason a character is refusedEvtl. vergeben @baphomello hat das vor 1 Tag übernommen. Offen
Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 84/100
Maintainer antworten meist innerhalb von 1 Tag