Fortran assignment on declaration and SAVE attribute gotcha

by

I don’t think that there is some rationale behind such behavior.

But as far as I know, Stefano, you used wrong terminology. In your code there is no assignment statement only variable (var) initialization using initialization expression (0).

integer :: var = 0 ! type declaration & initialization

integer :: var ! type declaration
var = 0        ! assignment

So it seems that it was just committee design decision. If we have such expression (with equality sign in type declaration statement) it is initialization not assignment. And initialization takes place only once during program (and not procedures) execution.

However there might be some historical reasons for such decision. Take a look at this thread.

Today such behavior is dangerous because many other widely used languages follows another conventions about initialization/assignment.

More Related Contents:

  1. Fortran running error
  2. Fortran 90 kind parameter
  3. Why Segmentation fault is happening in this openmp code?
  4. Unexpected “padding” in a Fortran unformatted file
  5. What is an undefined reference/unresolved external symbol error and how do I fix it in Fortran?
  6. Is There a Better Double-Precision Assignment in Fortran 90?
  7. MPI_Recv overwrites parts of memory it should not access
  8. changing array dimensions in fortran
  9. Sending 2D arrays in Fortran with MPI_Gather
  10. Fortran OpenMP program shows no speedup of CPU_TIME()
  11. Function has no implicit type
  12. Why is this a function declared inside the module and then used somewhere else in the same module not seen by the linker?
  13. Does Fortran have undefined behavior?
  14. What are the ways to pass a set of variable values through the subroutine to a function without common block?
  15. how to write wrapper for ‘allocate’
  16. gfortran does not allow character arrays with varying component lengths
  17. How do I do big integers in Fortran?
  18. What does “real*8” mean?
  19. Line truncated, Syntax error in argument list
  20. Fortran IF statement with numbers/labels rather than another statement
  21. Using a deferred-length character string to read user input
  22. Providing an argument that has not the TARGET attribute to a procedure with a dummy argument that has the TARGET attribute
  23. Strange label usage for an IF condition in a DO loop [duplicate]
  24. Difference between intent(out) and intent(inout)
  25. Fortran intent(inout) versus omitting intent
  26. Is Fortran unable to do the addition between 865398.78 and -865398.78? Why the answer is -0.03?
  27. Using do loop in a Fortran 90 program to read different number of lines for n frames?
  28. Allocatable array valued function. gfortran vs ifort
  29. How to pass subroutine names as arguments in Fortran?
  30. Confusing double precision real in Fortran

Leave a Comment