Intel® Fortran Compiler
Build applications that can scale for the future with optimized code designed for Intel® Xeon® and compatible processors.
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.

Interfaces

JohnNichols
Valued Contributor II
255 Views

I am using a lot more modules for data, and the subroutines,  is it a good idea to always use interfaces?

Just checking.

0 Kudos
5 Replies
FortranFan
Honored Contributor II
240 Views

Re "is it a good idea to always use interfaces?" - yes, absolutely.

mecej4
Black Belt
231 Views

When subroutines and functions in a module are accessed by USE <module_name> in a "consumer" of that module, an interface is already available, so there is no need to provide an interface block. Similarly, any procedure that is in a module has interfaces for other procedures in that module without your having to write interface blocks.

Steve_Lionel
Black Belt Retired Employee
201 Views

My position is that, with a couple of exceptions, if you're writing an interface block for a Fortran procedure in your own application, you're doing it wrong. Exceptions are declarations of generic procedures and when using submodules. Otherwise, your procedures should be in modules (or contained), in which case, as @mecej4 says, you get the explicit interface automatically.

I have written about interfaces twice: Doctor Fortran Gets Explicit! and Doctor Fortran Gets Explicit – Again!

JohnNichols
Valued Contributor II
193 Views
JohnNichols
Valued Contributor II
187 Views

Some unspecified AT&T weenie

-------------------------------------------------------------------

Found in a file from an internet source, quite disturbing in a way 

Reply