Re: Is this actually possible?

["Randy Brukardt" <randy@rrsoftware.com>]

"Lucretia" <laguest9000@googlemail.com> wrote in message 
news:69c7677b-4aec-4db2-b240-de6b69f762b9@googlegroups.com...
> On Wednesday, 11 December 2019 17:38:40 UTC, Dmitry A. Kazakov  wrote:
>> On 2019-12-11 17:43, Lucretia wrote:
...
>> > The idea is to export an array of tagged types as a C array to either a 
>> > function or a variable / struct element. i.e.
>>
>> Ada objects of tagged types have varying size and keep tag inside. Both
>> make them utterly incompatible with C.
>
> I know this, but as the compiler let it go through, I wondered if the tag 
> would be stored elsewhere and not with the tagged type. Otherwise, 
> shouldn't the compiler complain?

I don't know of any reason that a tagged record couldn't be compatible with 
C. It's just a record with an extra component for the tag, so if an untagged 
record would be compatible, then the same tagged record would be, too. (Of 
course, C couldn't do anything with the tag.)

Many Ada compilers let one move the tag to other locations (by using a 
record rep. clause to put the other components in specific places). I don't 
believe that GNAT supports that, however. But the C could use a junk field 
to take up the space of the tag to get the representations to match.

I'm not aware of any Ada compilers that can store the tag outside of the 
record. The need for tag re-emergence makes that nearly impossible (one 
would have to prove that no one ever will convert the type to a class-wide 
type anywhere in the program before it would be safe to put the tag outside 
of the object).

One can argue about the wisdom of requiring re-emergence in these cases, but 
we're stuck it (and some people think it is a good thing).

                                Randy.