Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Generate headers from ILE C headers

Abierto
  • ¿Algo no está bien?
#6 2 comentarios 0 reacciones 0 asignados Ver en GitHub

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
25/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
c, cpp
Área
compilers, tooling

Línea de trabajo

No implementation file or test is identified in the issue. Start by examining the existing PGMFunction and ILEFunction wrappers, then evaluate the proposed tree-sitter or libclang parsing and preprocessing paths, including ILE C system headers and ABI rules. Done would mean a defined approach for generating wrappers and preserving structures, macros, and layout.

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

Descripción

While this makes calling programs/procedures pretty easy, you might still need to copy and paste (and adapt) structure definitions and still write the PGMFunction/ILEFunction definitions. What'd be nice is being able to point to a header and extract definitions.

Likely challenges:

  • Turn function definitions into the previously mentioned wrappers, preserve structures. Preserve macros perhaps too, since they may be used for i.e. enum fields. Unsure of function pointer types, or data symbols (we need a wrapper type for this).
  • Deal with ILE C extensions, i.e. _Packed that are present in system headers. Either handle them in parsing or preprocess to convert them to the GCC extensions (which are still incompatible with strict standard C parsers...).
  • Preserve ABI layout in the AIX version of the structure. long is 32-bit in ILE C, and pointers are 128-bit (well, unless Teraspace is used, but there are pragmas to control this).
  • It might be wise to run the preprocessor (or at least unifdef) ahead of time, since there are some funny constructs that trip up i.e. tree-sitter and libclang unless we do that (i.e. use #ifdef for using #pragma for linkage control rather than extern "OS for OPM).
    • This means figuring out what stock definitions we need to set, what pragmas we need to keep and understand.
    • For #include, make sure we're importing the ILE C and not OS one (for i.e. sys/types.h. This likely means making a copy of the system headers and dumping them into a sysroot for GCC CPP (and hoping GCC CPP can understand), or a C preprocessor that we have finer grained control of.

What would be nice is an IDL for system APIs that we can generate from rather than parsing C, but that precludes user things (unless they conform to said IDL).

Lenguaje dominante
C++
Estrellas
3
Forks
0
Sin PR fusionados en 30 d

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 SeidenGroup/pase-cpp

Todos los issues de SeidenGroup/pase-cpp

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.