- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
I am using a lot more modules for data, and the subroutines, is it a good idea to always use interfaces?
Just checking.
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re "is it a good idea to always use interfaces?" - yes, absolutely.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
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!
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Some unspecified AT&T weenie
-------------------------------------------------------------------
Found in a file from an internet source, quite disturbing in a way
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page