F03 C interop..

[Richard E Maine]

On Sep 29, 2005, at 10:23 AM, Christopher D. Rickett wrote:

> Do you know what the plan is for implementing intrinsic modules?  Can 
> they
> simply be modules that are built by the compiler during the build 
> process of
> gfortran itself?

I could be wrong (and I don't know anything specific about gfortran 
plans anyway), but I don't think there is anything about the 
ISO_C_BINDING module that fundamentally has to be integrated with the 
compiler. That is, the compiler doesn't necessarily need to "know" much 
about the module. One could implement the module separately, with the 
only implication of intrinsicness being that it is found properly when 
INTRINSIC is specified on a USE statement (which could be done just by 
having a special directory that the compiler knows to look in).

Basically, for this module, "intrinsic" means very little other than 
"provided with the compiler", plus "looked for in the right module 
search order". I don't know what, if any gfortran plans have been made, 
but I think it *could* be done this way.

The IEEE modules have other "issues" in that USEing them can change 
compiler operation in ways that user modules just can't do.

Parsing and using the BIND(C) syntax is also necessary to go very far 
with the f2003 interop stuff, but that's a separate issue from the 
module.

-- 
Richard Maine                |  Good judgment comes from experience;
Richard.Maine@nasa.gov       |  experience comes from bad judgment.
                             |        -- Mark Twain