Epic: cobolrt as a product — a COBOL runtime for Java that carries its own evidence

Aperta
  • Qualcosa non va?
#4,710 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
6/100
Tipo di issue
Funzionalità
Chiarezza
Da chiarire
Stato di attività
Attiva
Stack tecnologico
java
Ambito
compilers

Direzione di ricerca

This is a tracking epic with no files or tests named, so there is no single starting point. Begin with the principles it links (#4702 for the IBM reference and z/OS calibration, #4704 for compile and runtime options) and with the first child issue, #4711, the rule catalogue. The epic is done when every checklist item is closed, and each item needs its own scoped issue before anyone starts work.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

enhancement epic legacy-modernization priority: high

Goal. Make cobolrt, the Java runtime that gives translated code COBOL's exact behaviour, a distinctive product. It's faithful to IBM z/OS under each estate's options, it carries its own evidence, it produces maintainable Java, and it offers customers an exit route instead of lock-in.

Why. Translation fidelity is almost entirely the runtime's job: nearly every correctness bug fixed on 2026-10-07/08 was a runtime rule. Competitors ship proprietary runtimes that customers must trust and license forever. Ours can be provable, customer-owned and option-aware.

Principles.

  • IBM is the reference; GnuCOBOL is the instrument (#4702).
  • Options are a first-class input (#4704).
  • Fail loudly, never silently.

Issues

  • #4711 rule catalogue: an ID, IBM reference, options and register status per rule
  • #4712 rules as data: generate code, vectors and docs (first family)
  • #4713 evidence report: the rules each program exercises, with calibration status
  • #4714 per-estate options profile in the runtime (builds on #4704)
  • #4715 more readable Java: provably-safe lifting
  • #4716 exit route: production quirk telemetry, then a simplification report
  • #4717 performance benchmark plus proven fast paths
  • #4718 runtime as a shippable product: API, versioning, licence, docs, fail-loudly audit

Related.

  • #4702: IBM reference and z/OS calibration.
  • #4704: compile and runtime options.
  • #4601 / #4703: evidence report.
  • #4628: det-port mutation (L5).

Suggested order. 4711 → 4712 (with #4702 calibration) → 4713 and 4714 → 4717 → 4715 / 4716 → 4718 (the licence question runs in parallel with counsel).

🤖 Generated with Claude Code

Lingua principale
Python
Stelle
57
Fork
11
Merge medio
1h 35m
PR unite (30g)
975

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di squid-protocol/gitgalaxy

Tutte le issue di squid-protocol/gitgalaxy

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.