Why is this a function declared inside the module and then used somewhere else in the same module not seen by the linker?

by

In the following, I’ll explain using the complete example below (which you can compile and link to try things):

module mymodule
contains
  integer function foo ()
    foo = 1
  end function

  integer function bar ()
    integer :: foo
    bar = foo()
  end function
end module

program test
  use mymodule
  print *, bar()
end

In the code of function bar, the declaration integer :: foo is strictly equivalent to:

integer, external :: foo

Thus, in the code of bar, you are explicitly stating:

“there may already be a symbol of name
foo accessible to you, but from now
on, when I use it I mean it to be an
external function of this name”

So, this is valid code, and the compiler just expect you to provide an external function named foo. Because you don’t (the module function isn’t external), it fails to link. You can provide an external foo function by adding the following code (not in the module, just at the end of the same file):

integer function foo ()
  foo = 42
end function

If you add this function body, then your code will compile, and the output will be 42 (as the external function is called, not the module function).

Also worth noting, if you comment out integer :: foo line in the code of bar, symbol foo will resolve to the module function, which will then be called whether or not you provide an external function named foo (thus, the output will be 1).

Conclusion: not a compiler bug, but misuse of an old feature of the language (external declarations). To be honest, I think it’s better to explicitly mark your external declarations as such, which would at least have highlighted the issue here.

More Related Contents:

  1. Where to put `implicit none` in Fortran
  2. gfortran does not allow character arrays with varying component lengths
  3. Reading writing fortran direct access unformatted files with different compilers
  4. Error: Nonnegative width required in format string at (1)
  5. Fortran array cannot be returned in function: not a DUMMY variable
  6. Allocatable array valued function. gfortran vs ifort
  7. Fortran 90 kind parameter
  8. Unexpected “padding” in a Fortran unformatted file
  9. Fortran assignment on declaration and SAVE attribute gotcha
  10. MPI_Recv overwrites parts of memory it should not access
  11. Fortran OpenMP program shows no speedup of CPU_TIME()
  12. Function has no implicit type
  13. ‘*’ and ‘/’ not recognized on input by a read statement
  14. Why are my random numbers always the same?
  15. What are the ways to pass a set of variable values through the subroutine to a function without common block?
  16. how to write wrapper for ‘allocate’
  17. How do I do big integers in Fortran?
  18. What is the purpose of result variables in Fortran?
  19. Line truncated, Syntax error in argument list
  20. Using a deferred-length character string to read user input
  21. Strange label usage for an IF condition in a DO loop [duplicate]
  22. Mac OS X R error “ld: warning: directory not found for option”
  23. Fortran OpenMP with subroutines and functions
  24. Fortran print allocatable array in gdb
  25. How to override a structure constructor in fortran
  26. Using do loop in a Fortran 90 program to read different number of lines for n frames?
  27. Specify directory where gfortran should look for modules
  28. Passing size as argument VS assuming shape in Fortran procedures
  29. Fortran SAVE statement
  30. MPI_Gather gives seg fault in the most basic code

Leave a Comment