topic DLLEXPORT overloaded interface. in Intel® Fortran Compiler

DLLEXPORT overloaded interface.

Ilie__Daniel — Mon, 18 Jun 2012 16:53:21 GMT

Hello!

In a DLL I have code that performs real and complex number addition.
I put the two subroutines (real and complex addition) in a module and overloaded the interface.
The problem is that I want to export only one routine, i.e. the overloaded interface.

I included the code below:

moduleoutput
implicitnone
private

public::add
 
 
!dec$attributesdllexport,c,reference,alias:'add'::add
interfaceadd
moduleprocedureradd,cadd
endinterfaceadd

contains
 
subroutineradd(a,b,x)
implicitnone

real,intent(in)::a,b
real,intent(out)::x

x=a+b

endsubroutineradd
 
subroutinecadd(a,b,x)
implicitnone

complex,intent(in)::a,b
complex,intent(out)::x

x=a+b

endsubroutinecadd

endmoduleoutput

How do I export the overloaded interface "add"?

Thank you for your suggestions.

DLLEXPORT overloaded interface.

Steven_L_Intel1 — Mon, 18 Jun 2012 17:14:09 GMT

You don't - that's not how it works. Your module makes "add" the only public symbol for users of the module. But you must export from the DLL all of the specific routines that "add" can resolve to. "add" is not a callable routine, it's a generic interface that the compiler sorts out.

DLLEXPORT overloaded interface.

Ilie__Daniel — Tue, 19 Jun 2012 14:34:05 GMT

Ok. Thank you Steve.
I exported each routine individually and added this to the main program:

interfaceadd
subroutineradd(a,b,x)
!dec$attributesdllimport,c,reference,alias:'radd'::radd
!dec$attributesreference::a,b,x
implicitnone

real,intent(in)::a,b
real,intent(out)::x
endsubroutineradd
 
subroutinecadd(a,b,x)
!dec$attributesdllimport,c,reference,alias:'cadd'::cadd
!dec$attributesreference::a,b,x
implicitnone

complex,intent(in)::a,b
complex,intent(out)::x
endsubroutinecadd
endinterfaceadd

Everything works fine now.

DLLEXPORT overloaded interface.

Steven_L_Intel1 — Tue, 19 Jun 2012 14:59:40 GMT

If you used a module for your routines, just USE the module in the main program. You should never have to repeat the interface. The DLLEXPORTs will magically turn into DLLIMPORTs on the USE.

DLLEXPORT overloaded interface.

Ilie__Daniel — Tue, 19 Jun 2012 15:29:00 GMT

Ok, but this works only if I include the path to the compiled module file (output.mod). This is in addition to referencing the .lib in the main program, which I did before anyway.

DLLEXPORT overloaded interface.

Steven_L_Intel1 — Tue, 19 Jun 2012 15:50:25 GMT

Yes - typically you would provide the LIB and MOD to the user of your code. If you make the library project a dependent of the main project, the compiler will see the .mod file from the library automatically (that is new in Composer XE 2011).