This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
tutorials:fortran [2014/01/11 02:30] papa [Input/Output Devices] |
tutorials:fortran [2022/03/19 09:52] papa [CPU/Elapsed time report on program termination] |
||
---|---|---|---|
Line 9: | Line 9: | ||
===== Peculiarities ===== | ===== Peculiarities ===== | ||
+ | ==== CPU/Elapsed time report on program termination ==== | ||
+ | |||
+ | The FORTRAN compiler adds a report on CPU and elapsed time used by the program that prints at the end of every program run, like: | ||
+ | |||
+ | CPU time 0.08 Elapsed time 0.09 | ||
+ | |||
+ | This message can be suppressed by adding the following line to your program source: | ||
+ | |||
+ | CALL QUIETX | ||
+ | |||
+ | ==== DATE subroutine bug ==== | ||
+ | |||
+ | Although the TOPS-20 operating system as a whole survived the Y2K crisis, the FORTRAN DATE subroutine did not fare as well. | ||
+ | |||
+ | DATE is supposed to return a ten-character string representing the current system date with the format: | ||
+ | |||
+ | '' | ||
+ | |||
+ | Where: | ||
+ | |||
+ | | '' | ||
+ | | '' | ||
+ | | '' | ||
+ | | '' | ||
+ | |||
+ | However, since the year 2000, the DATE has set the '' | ||
+ | |||
+ | This renders the year portion of DATE's output useless for most purposes. A work-around is to program a date subroutine in another language that correctly processes the TOPS-20 system date (such as MACRO assembly language) and call that subroutine from your FORTRAN program instead of the FORTRAN DATE subroutine. | ||
==== Input/ | ==== Input/ |