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

Abierto
  • ¿Algo no está bien?
#4,710 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
6/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
java
Área
compilers

Línea de trabajo

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.

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

Descripción

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

Lenguaje dominante
Python
Estrellas
57
Forks
11
Merge medio
1 h 35 min
PR fusionados (30 d)
975

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 squid-protocol/gitgalaxy

Todos los issues de squid-protocol/gitgalaxy

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.