[Fortran, RFC patch] Document naming and argument passing convention

[Tobias Burnus]

Ups - I attached the wrong patch (same file name, wrong directory). 
Hopefully, this one is the correct one.

Tobias

Am 29.03.2013 19:40, schrieb Tobias Burnus:
> Dear all,
>
> the attached patch attempts to document gfortran's naming and argument 
> passing convention when Bind(C) is not used.
>
> While Bind(C) is the recommended way for interoperation with other 
> Fortran compilers and other languages, there are situations where this 
> is not possible; for instance, legacy code. Or in case of the MPI 
> standard, the MPI implementation might need this information and MPI 
> performance tool developers (PMPI) have to know how the different 
> Fortran compilers pass the arguments.
>
> The attached patch does not (yet) state how array descriptors are 
> handled internally. (I was thinking of deferring this until the new 
> array descriptor becomes available.) I also believe there are other 
> omissions as well and the wording could be improved. Suggestions are 
> welcome.
>
> The patch was motivated by Walter's comment** to my VALUE+OPTIONAL 
> patch.* It takes his comments into account and, that part, only 
> reflects gfortran's implementation after the VALUE+OPTIONAL patch has 
> been committed with his suggested change.
>
> What do you think?
>
> Tobias
>
> * http://gcc.gnu.org/ml/fortran/2013-03/msg00102.html
> ** http://gcc.gnu.org/ml/fortran/2013-03/msg00173.html

-------------- next part --------------
A non-text attachment was scrubbed...
Name: gfortran-texi.diff
Type: text/x-patch
Size: 6865 bytes
Desc: not available
URL: <http://gcc.gnu.org/pipermail/fortran/attachments/20130329/8e5430bc/attachment.bin>