FTN95 provides a load-and-go facility via the /LGO compiler option so that programs can be quickly compiled, loaded and executed. /LGO can be used with large and complex programs, even those that require the use of libraries. No permanent object or executable file is produced (although there must be enough disk space to accommodate a temporary object file). These features make this facility invaluable for teaching, testing and development where repeated compi lations and test runs are the norm.
If you wish to keep a copy of the current executable file then the /LINK option should be used. /LINK has no effect when used with /LGO.
Most of the other compiler options are available together with a number of extra options which allow the following:
specification of relocatable binary library and input files,
underflow trapping,
interactive debugging.
The load-and-go facility is invoked by the /LGO option. For example:
FTN95 MYPROG /CHECK /LGO
would compile, load and execute the program held in the source file MYPROG.F90. The order of options on the command line is immaterial, except when an option requires a name, in which case the name must follow it.
The Win32 options /BREAK and /DBREAK both imply /LGO. These options also imply either /DEBUG or /CHECK.
These options are summarised in the following table for easy reference.
Option |
Debug code planted |
Check code planted |
Immediate entry to debugger |
/LGO implied |
/DEBUG |
yes |
|
|
|
/CHECK |
yes |
yes |
|
|
/BREAK (Win32) |
yes |
yes |
yes |
yes |
/DBREAK (Win32) |
yes |
|
yes |
yes |