This will finish out the rest of the "specification_part" of a Fortran program. Once this is completed I can move on to supporting function and subroutines which will reuse the "specification_part". Additionally, it may be worthwhile to make a separate "executable_part" that can be reused in them as well.
use statement syntaxes
USE ISO_C_BINDING
USE ISO_FORTRAN_ENV, ONLY : ERROR_UNIT, OUTPUT_UNIT
Include statements have to be followed by a character literal, they can also appear anywhere in the program as they are similar in nature to pre-processor directives.
Additional details on include statements: https://gcc.gnu.org/onlinedocs/gcc-3.4.4/g77/INCLUDE.html
undefined, static and automatic values in the implicit statement cause an error so I am going to drop them which will allow me to use basic intrinsic types.
This will finish out the rest of the "specification_part" of a Fortran program. Once this is completed I can move on to supporting function and subroutines which will reuse the "specification_part". Additionally, it may be worthwhile to make a separate "executable_part" that can be reused in them as well.
use statement syntaxes
Include statements have to be followed by a character literal, they can also appear anywhere in the program as they are similar in nature to pre-processor directives. Additional details on include statements: https://gcc.gnu.org/onlinedocs/gcc-3.4.4/g77/INCLUDE.html
Implicit statements have a similar design to equivalence statements. See: https://docs.oracle.com/cd/E19957-01/805-4939/6j4m0vn9v/index.html