home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!mcsun!news.funet.fi!hydra!klaava!cc.helsinki.fi!sundius
- From: sundius@cc.helsinki.fi
- Newsgroups: comp.lang.fortran
- Subject: Re: Why CALL EXIT? (was Re: Question for C ==> Fortran)
- Message-ID: <1992Jul31.103917.1@cc.helsinki.fi>
- Date: 31 Jul 92 08:39:17 GMT
- References: <1992Jul29.134901.1@slacvx.slac.stanford.edu> <131935@lll-winken.LLNL.GOV> <30JUL199215540929@ltp2.gsfc.nasa.gov> <6881@charon.cwi.nl>
- Sender: news@klaava.Helsinki.FI (Uutis Ankka)
- Organization: University of Helsinki
- Lines: 23
-
- In article <6881@charon.cwi.nl>, dik@cwi.nl (Dik T. Winter) writes:
- > Well, I know of systems were you get a non-zero exit status if your program
- > does not terminate with a STOP statement.
- > --
-
- According to the FORTRAN 77 standard (ANSI X3.9-1978), the STOP statement
- causes the termination of execution of the executable program, and the
- END statement (when executed in the main program) terminates the execution
- of the executable program (pp. 11-9, 11-10). The STOP statement has an
- additional digit string or character constant which is "accessible" at
- the time of termination. According to page B-6 in the appendix, the
- availability of this string depends on the processor. I could not find
- any reference to the CALL EXIT statement at all.
-
- It thus seems that the omission of the STOP statement is fully permissible
- according to the standard.
-
-
- +--------------------------------------------------------------------+
- ! Tom Sundius Department of Physics !
- ! Internet: sundius@cc.helsinki.fi University of Helsinki !
- ! BitNet: SUNDIUS@FINUH SF-00170 Helsinki, Finland !
- +--------------------------------------------------------------------+
-