Difference between intent(out) and intent(inout)

by

intent(inout) and intent(out) are certainly not the same. You have noted why, although you don’t draw the correct conclusion. On entering the subroutine useless a is undefined, rather than defined.

Having a variable “undefined” means that you cannot rely on a specific behaviour when you reference it. You observed that the variable a had a value 5 but this does not mean that the only value you could observe is 5. In particular “undefined” does not mean “takes a specific value like NaN”.

Your code is not standard conforming because of this reference to an undefined variable. See Fortran 2008 6.2 (similar meaning will be somewhere in Fortran 90 as initially tagged). Of particular note is that the compiler doesn’t have to point out your mistake.

With intent(inout) the variable a would be defined when referenced and it will be guaranteed to have the value 5 (for a conforming processor).

More widely, there are other differences between the two intent attributes and this “coincidental” appearance of the similarity of the definition of the variable a could be more troublesome.

Allocatable arrays and objects with deferred type parameters, for example, are deallocated; derived types become undefined (and any allocatable components deallocated) and components with default initialization are “re-initalized”; pointers have their association status become undefined.

All of these latter things have potential for very awkward results, much more so than with a scalar integer, if they are referenced without being defined first.

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. Fortran assignment on declaration and SAVE attribute gotcha
  8. MPI_Recv overwrites parts of memory it should not access
  9. Sending 2D arrays in Fortran with MPI_Gather
  10. Print to standard output from a function defined in an Fortran module
  11. Why is this a function declared inside the module and then used somewhere else in the same module not seen by the linker?
  12. Does Fortran have undefined behavior?
  13. Reading data file in Fortran with known number of lines but unknown number of entries in each line
  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. Fortran intent(inout) versus omitting intent
  24. Is Fortran unable to do the addition between 865398.78 and -865398.78? Why the answer is -0.03?
  25. Using do loop in a Fortran 90 program to read different number of lines for n frames?
  26. Passing size as argument VS assuming shape in Fortran procedures
  27. Allocatable array valued function. gfortran vs ifort
  28. How to pass subroutine names as arguments in Fortran?
  29. MPI_Gather gives seg fault in the most basic code
  30. Confusing double precision real in Fortran

Leave a Comment