(j3.2006) (SC22WG5.3789) [ukfortran] N1761, TYPE(*), BIND(C) and arrays

[N.M. Maclaren]

On Dec 9 2008, Reinhold Bader wrote:
>
>It appears to me that if non-interoperable arguments are to be allowed,
>it will be necessary to include interoperability among the
>characteristics of the dummy arguments if a clean, extensible
>design is favored.

Yes, indeed, though there are many ways of doing it.  And, with the
approach of N1761, there aren't just interoperable and non-interoperable
but several intermediate states.

>This would probably also mesh nicely with the concept of creating
>mapped (as opposed to matching) interfaces in case at least one
>of the arguments is non-interoperable. And it would cover the
>problematic case of a scalar non-interoperable entity as well.

Careful design would be needed, and I should be happy to work with people
on that.

>Of course, for the TR many limitations can be imposed on what kinds
>of non-interoperable entities are allowed. In particular I agree that
>additional restrictions will be needed for TYPE(*) dummies in BIND(C)
>interfaces to prevent accidents from happening to the poor C programs
>who are being served monsters and non-monsters in turn to the same
>interface, within the same program.

Indeed.  But they haven't been.  I don't think N1761 is ready to be
considered as a draft TR.


Regards,
Nick Maclaren,
University of Cambridge Computing Service,
New Museums Site, Pembroke Street, Cambridge CB2 3QH, England.
Email:  nmm1 at cam.ac.uk
Tel.:  +44 1223 334761    Fax:  +44 1223 334679