Fortran intent(inout) versus omitting intent

by

According to The Fortran 2003 Handbook by Adams, et al., there is one difference between an intent(inout) argument and argument without specified intent. The actual argument (i.e., in the caller) in the intent(inout) case must always be definable. If the intent is not specified, the argument must be definable if execution of the subroutine attempts to define the dummy argument. definable means setting the value: dummy_arg = 2.0. Clearly the actual argument should be a variable if this is done. For intent(inout) the actual argument must be definable whether or not the subroutine does this. Without no intent specified, it depends on what happens on that particular invocation of the subroutine — if the subroutine doesn’t define the variable, it is OK; if it does, than there is a problem — cases such as writing to an actual argument that is a constant will obviously cause problems.

This doesn’t mean that the compiler will diagnose all of these cases — what the standard requires a compiler to diagnose is a different issue. It would be close to impossible to detect all errors of the intent-not-specified case requirement at compile time, since violations depend on the run-time flow of the code. It is much easier for the compiler to diagnose the intent(inout) case and warn you of problems with the code.

More Related Contents:

  1. Is There a Better Double-Precision Assignment in Fortran 90?
  2. Where to put `implicit none` in Fortran
  3. What are the ways to pass a set of variable values through the subroutine to a function without common block?
  4. gfortran does not allow character arrays with varying component lengths
  5. What does “real*8” mean?
  6. What is the purpose of result variables in Fortran?
  7. Fortran IF statement with numbers/labels rather than another statement
  8. Function in fortran, passing array in, receiving array out
  9. Fortran array cannot be returned in function: not a DUMMY variable
  10. Is Fortran unable to do the addition between 865398.78 and -865398.78? Why the answer is -0.03?
  11. Using do loop in a Fortran 90 program to read different number of lines for n frames?
  12. Fortran SAVE statement
  13. Fortran 90 kind parameter
  14. Unexpected “padding” in a Fortran unformatted file
  15. Correct use of modules, subroutines and functions in Fortran
  16. Fortran assignment on declaration and SAVE attribute gotcha
  17. MPI_Recv overwrites parts of memory it should not access
  18. How to initialize two-dimensional arrays in Fortran
  19. Assumed size arrays: Colon vs. asterisk – DIMENSION(:) arr vs. arr(*)
  20. What flags do you set for your GFORTRAN debugger/compiler to catch faulty code?
  21. how to write wrapper for ‘allocate’
  22. How do I do big integers in Fortran?
  23. Line truncated, Syntax error in argument list
  24. Using a deferred-length character string to read user input
  25. Providing an argument that has not the TARGET attribute to a procedure with a dummy argument that has the TARGET attribute
  26. Strange label usage for an IF condition in a DO loop [duplicate]
  27. Difference between intent(out) and intent(inout)
  28. Passing size as argument VS assuming shape in Fortran procedures
  29. Allocatable array valued function. gfortran vs ifort
  30. MPI_Gather gives seg fault in the most basic code

Leave a Comment