(j3.2006) (SC22WG5.3585) OPTIONAL arguments and C interop

Van Snyder Van.Snyder
Wed Jul 16 14:16:52 EDT 2008

On Wed, 2008-07-16 at 09:47 -0500, Bill Long wrote:
> A side effect of this design is that OPTIONAL and VALUE cannot be both
> specified for a particular dummy argument.


I don't understand this problem.

I would think that processors could use their Fortran conventions for
argument forms that don't exist in C, i.e., assumed-shape arrays,
optional arguments, and optional+value arguments.  The TR would specify
functions or structs to access and create such arguments.  Preferably
functions, so that vendors can provide them according to their Fortran
conventions, instead of changing their Fortran conventions to conform to
structs specified by the TR for the BIND(C) case.


More information about the J3 mailing list