home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.fortran
- Path: sparky!uunet!sun-barr!cs.utexas.edu!uwm.edu!csd4.csd.uwm.edu!jgd
- From: jgd@csd4.csd.uwm.edu (John G Dobnick)
- Subject: Re: Why CALL EXIT? (was Re: Question for C ==> Fortran)
- Message-ID: <1992Jul30.171640.11691@uwm.edu>
- Originator: jgd@csd4.csd.uwm.edu
- Sender: news@uwm.edu (USENET News System)
- Reply-To: jgd@csd4.csd.uwm.edu
- Organization: University of Wisconsin - Milwaukee
- References: <1992Jul29.204115.3917@walter.cray.com>
- Date: Thu, 30 Jul 1992 17:16:40 GMT
- Lines: 26
-
- From article <1992Jul29.204115.3917@walter.cray.com>, by wws@craywr.cray.com (Walter Spector):
- >
- > This is something I have never understood in almost 20 years of Fortran
- > programming. Why do so many people use the non-standard CALL EXIT
- > instead of the standardized-for-over-25-years STOP statement?
- > Is/was there magic associated with it on some arcane systems?
-
-
- Not so much "arcane" systems, as "old" systems. On older systems,
- CALL EXIT was a return to the Monitor (or Operating System, if you
- wish to call it that). STOP, on the other hand, did just that --
- it _stopped_ the machine! This is clearly an unpopular thing to do
- on a multi-user system, but most of these older systems were,
- effectively, single user, with the user standing right in front of
- the machine.
-
- I suspect the continued use of CALL EXIT is more habit than anything else.
-
- --
- John G Dobnick ATTnet: (414) 229-5727
- Computing Services Division INTERNET: jgd@uwm.edu
- University of Wisconsin - Milwaukee UUCP: uunet!uwm!jgd
-
- "Knowing how things work is the basis for appreciation,
- and is thus a source of civilized delight." -- William Safire
-
-