Re: Record representation : components order

[Stephen Leake <stephen_leake@stephe-leake.org>]

sjw <simon.j.wright@mac.com> writes:

> On Jul 9, 10:28�am, Stephen Leake <stephen_le...@stephe-leake.org>
> wrote:
>> sjw <simon.j.wri...@mac.com> writes:
>
>> > * in theory tcladashell is compiler-independent.
>>
>> That's not important. You only need to generate the Ada code once
>> (well, once each time the C code changes); then you can use it with
>> any compiler. So only the tcladashell maintainer/developer needs
>> -fdump-ada-spec.
>
> This is perhaps an unusual example, and I'm not sure it would actually
> happen, but:
>
> struct {
>   int i;
> #ifdef SOME_BIZARRE_COMPILER_I_DONT_HAVE_BUT_YOU_DO
>   int j;
> #endif
> } foo;

More likely the #ifdef is on the OS; for example, the "fstat" struct
has different components on different operating systems. In either
dase, the solution is the same as below.

>
> Also, I tried 'gcc -fdump-spec /usr/include/tcl.h' and got the
> following out:
>
> i386_utypes_h.ads
> stdarg_h.ads
> stdio_h.ads
> sys_utypes_h.ads
> tcl_h.ads
> tcldecls_h.ads
> tclplatdecls_h.ads
> utypes_h.ads
>
> and stdio_h.ads contains eg
>    subtype size_t is i386_utypes_h.uu_darwin_size_t;
>
> so I could hardly hope that would work with Aonix on Windows!

Ok, so you need to keep track of separate Ada files for each target,
where a target is a combination of Ccompiler and OS.

You still only run -fdump-ada-spec when the C code changes.
-- 
-- Stephe