home *** CD-ROM | disk | FTP | other *** search
/ NetNews Usenet Archive 1992 #16 / NN_1992_16.iso / spool / comp / lang / fortran / 2878 < prev    next >
Encoding:
Text File  |  1992-07-30  |  1.2 KB  |  34 lines
  1. Newsgroups: comp.lang.fortran
  2. Path: sparky!uunet!usc!noiro.acs.uci.edu!network.ucsd.edu!sdcrsi!equalizer!timbuk.cray.com!walter.cray.com!craywr!wws
  3. From: wws@craywr.cray.com (Walter Spector)
  4. Subject: Why CALL EXIT? (was Re: Question for C ==> Fortran)
  5. Message-ID: <1992Jul29.204115.3917@walter.cray.com>
  6. Sender: wws@craywr (Walter Spector)
  7. Organization: Cray Research, Inc.
  8. References: <1992Jul28.075514.28683@debbie.cc.nctu.edu.tw> <1992Jul29.134901.1@slacvx.slac.stanford.edu>
  9. Date: 29 Jul 92 20:41:15 CDT
  10. Lines: 22
  11.  
  12.  
  13. In article <1992Jul29.134901.1@slacvx.slac.stanford.edu>, fairfield@slacvx.slac.stanford.edu writes:
  14. |> [a bunch of stuff, then...]
  15. |>         CALL EXIT
  16. |>         END
  17. |>
  18. |> The "CALL EXIT" at the bottom is optional (more-or-less). A "STOP" statement
  19. |> would do just as well.
  20.  
  21. This is something I have never understood in almost 20 years of Fortran
  22. programming.  Why do so many people use the non-standard CALL EXIT
  23. instead of the standardized-for-over-25-years STOP statement?
  24. Is/was there magic associated with it on some arcane systems?
  25.  
  26. (At least there aren't many codes twiddling 'sense lights' anymore. :-)
  27.  
  28. Walt
  29. -- 
  30. Walt Spector
  31. (wws@renaissance.cray.com)
  32. Sunnyvale, California
  33. _._ _._ _.... _. ._.
  34.