Re: Ada array vs C pointer (call by reference)

[Adam Beneschan <adam@irvine.com>]

On Jun 28, 7:04 am, Stephen Leake <Stephe.Le...@nasa.gov> wrote:
> Adam Beneschan <a...@irvine.com> writes:
> > On Jun 27, 3:14 pm, Keith Thompson <ks...@mib.org> wrote:
> >> Maciej Sobczak <see.my.homep...@gmail.com> writes:
> >> > On 27 Cze, 18:11, Keith Thompson <ks...@mib.org> wrote:
> >> > > > Ada *cannot* guarantee that Interfaces.C.C_Float is the *right* float,
> >> > > > because it does not verify how the C code was compiled and there is a
> >> > > > lot of freedom given to C implementers in this area.
> >> > > > Same for all other types.
>
> >> > > No, Ada can't guarantee it directly.  Instead, Ada requires the
> >> > > implementation to guarantee it.
>
> >> > And how the implementation can guarantee it without mandating the
> >> > representation on the C compiler?
>
> >> It doesn't *mandate* the representation used by the C compiler; the
> >> author of the Interfaces.C implementation has to *know* the
> >> representation used by the C compiler.
>
> > Which is, of course, impossible without a crystal ball.
>
> No, the vendor must provide both the Ada compiler and the C compiler.
> Are there any vendors out there that don't?

Yes.

                       -- Adam