[Fortran-experiments] Bind(c) first experiences

Tobias Burnus burnus@net-b.de
Wed Jan 17 18:52:00 GMT 2007


Hi Chris,

Christopher D. Rickett wrote:
> thanks for sending me your code.  i tried it out, and the output from 
> gfortran is similar to that of NAG.
Thanks. I probably have an too old version.
Your patch, http://gcc.gnu.org/ml/fortran/2007-01/msg00301.html is not
checked in yet, is it?
I probably should apply the patch first, before continue doing some tests.
Are there further changes or is that patch up to date?

  * * *

What is actually the procedure for applying patches to the branch?

(We should by the way also merge the trunk up to the branch and
consolidate the VALUE implementation.)

> I did not see the original line that you said NAG gave an error for that 
> gfortran did not ( type(c_funptr), pointer :: pnter ).  is that line part 
> of another test?
>   
Probably; I try to find my test case - or rewrite it (if I can figure
out what I did).

Regarding to your last patch,
http://gcc.gnu.org/ml/fortran/2007-01/msg00301.html

+ * to generate.         If <code>c_ptr</code> is given, then
<code>c_null_ptr</code>

I think the coding convention is not to use "<code>...</code>"  (at
least none of the other gfortran files do)

+static void gen_special_c_interop_ptrs (const char *kinds[],
+                                       const char *module_name)

If you use

+static void
+gen_special_c_interop_ptrs (const char *kinds[],

one can grep for    ^gen_special_c_interop_ptrs  to find the function
itself (and not the use of the function). This seems to be the coding
convention in gfortran.

Tobias



More information about the Fortran mailing list