‘*’ and ‘/’ not recognized on input by a read statement

by

FORTRAN input and output formatting rules are rather involved. Each input and ouptut statement has two arguments that have special meaning. For example

  READ (10,"(2I10)") m,n

The first argument is a file descriptor. Here it is 10. The second argument "(2I10)" is the format specifier. If you give an asterisk (*) as a format specifier you switch on the list-directed formatting mode.

List directed input as the name suggests is controlled by the argument list of the input operator.

1. Why asterisk (*) is special in list-directed input mode?

The input list is split into one or more input records. Each input record is of the form c, k*c or k* where c is a literal constant, and k is an integer literal constant. For example,

  5*1.01

as an instance of k*c scheme is interpreted as 5 copies of number 1.01

   5*

is interpreted as 5 copies of null input record.

The symbol asterisk (*) has a special meaning in list-directed input mode. Some compiler runtimes would report a runtime error when they encounter asterisk without an integer constant in list-directed input, other compilers would read an asterisk. For instance GNU Fortran compiler is known for standards compliance, so its runtime would accept *. Other compiler runtimes might fail.

2. What’s up with slash (/)?

A comma (,), a slash (/) and a sequence of one or more blanks ( ) are considered record separators in list-directed input mode.

There is no simple way to input a slash on its own in this mode.

3. Possible solution: specify format explicitly

What you can do to make the runtime accept a single slash or an asterisk is to leave the list-directed input mode by specifying the format explicitly:

read (*,"(A1)") oper

should let you input any single character.

More Related Contents:

  1. Fortran running error
  2. Fortran 90 kind parameter
  3. Fortran: integer*4 vs integer(4) vs integer(kind=4)
  4. Is There a Better Double-Precision Assignment in Fortran 90?
  5. Fortran assignment on declaration and SAVE attribute gotcha
  6. MPI_Recv overwrites parts of memory it should not access
  7. changing array dimensions in fortran
  8. Why should I use interfaces?
  9. Fortran OpenMP program shows no speedup of CPU_TIME()
  10. Where to put `implicit none` in Fortran
  11. Function has no implicit type
  12. Print to standard output from a function defined in an Fortran module
  13. Reading data file in Fortran with known number of lines but unknown number of entries in each line
  14. how to write wrapper for ‘allocate’
  15. gfortran does not allow character arrays with varying component lengths
  16. How do I do big integers in Fortran?
  17. What is the purpose of result variables in Fortran?
  18. Using a deferred-length character string to read user input
  19. Function in fortran, passing array in, receiving array out
  20. Reading writing fortran direct access unformatted files with different compilers
  21. Strange label usage for an IF condition in a DO loop [duplicate]
  22. Fortran OpenMP with subroutines and functions
  23. Error: Nonnegative width required in format string at (1)
  24. Fortran intent(inout) versus omitting intent
  25. Fortran array cannot be returned in function: not a DUMMY variable
  26. Is Fortran unable to do the addition between 865398.78 and -865398.78? Why the answer is -0.03?
  27. Passing size as argument VS assuming shape in Fortran procedures
  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