Re: Allocation interoperability (Fortran/C)
- From: Sebastian Hanigk <hanigk@xxxxxxxxx>
- Date: Fri, 15 Dec 2006 15:10:10 +0100
"Jugoslav Dujic" <jdujic@xxxxxxxxx> writes:
Hello!
I've written "my own" ISO_C_BINDING (for IVF and FTN95), but the problem is
that the ISO_C_BINDING.f90 is a cludge. Plus, it needs an additional wrapper
routine for every type (and TYPE) which is subject to C_F_POINTER conversion.
(C_F_POINTER itself is a generic interface).
So, it's mostly doable with F95+extensions+reverse engineering of array
descriptor, although the wrapper code is really ugly; the "user-side" code
is, however, F2003-compatible (AFAICT).
I can send you the code if you like.
I would be very much obliged if you could do so!
Thanks,
Sebastian
.
- References:
- Allocation interoperability (Fortran/C)
- From: Sebastian Hanigk
- Re: Allocation interoperability (Fortran/C)
- From: Steve Lionel
- Re: Allocation interoperability (Fortran/C)
- From: Sebastian Hanigk
- Re: Allocation interoperability (Fortran/C)
- From: Steve Lionel
- Re: Allocation interoperability (Fortran/C)
- From: Richard E Maine
- Re: Allocation interoperability (Fortran/C)
- From: Sebastian Hanigk
- Re: Allocation interoperability (Fortran/C)
- From: Jugoslav Dujic
- Allocation interoperability (Fortran/C)
- Prev by Date: Re: allocated array
- Next by Date: Re: Derived type - valued function with pointer member.
- Previous by thread: Re: Allocation interoperability (Fortran/C)
- Next by thread: Re: Allocation interoperability (Fortran/C)
- Index(es):
Relevant Pages
|