Re: Interfacing with C ; an ununsed fields dilemma

["Hibou57 (Yannick Duchêne)" <yannick_duchene@yahoo.fr>]

On 2 juil, 11:45, Maciej Sobczak <see.my.homep...@gmail.com> wrote:
> In some cases it is actually the only way to go, because in some C
> libraries the data structure layout can change from version to version
> and even though the proper layout is always defined in C header files,
> they are not *automatically* understood by Ada. You are not going to
> update your Ada wrapper every time, really.

For this single case, this API will not evolve anymore, as it has been
replaced by another, totaly different and incompatible with te two
previous versions... but which no body use.

The idea of a pre-wrapper before Ada is nice and clean (although at
the time, I prefer to not do this way, for some reasons)

> It is also the only way to interface with more elaborated C++
> libraries.
That's true, for C++, this would be mandatory (hope I will never have
to interface C++)


Finally, I think I will simply declare these unused fields in the
public part, in order to be able to give them an initialization value,
but I really do not like it to appears in the public part.