home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky vmsnet.internals:1238 vmsnet.misc:769
- Newsgroups: vmsnet.internals,vmsnet.misc
- Path: sparky!uunet!sun-barr!cs.utexas.edu!usc!wupost!tulane!cpu.com!cpu.com!GWLESTER
- From: gwlester@cpu.com (Gerald W. Lester)
- Subject: Re: Exit handlers in VAX-C
- Nntp-Posting-Host: merlin.cpu.com
- References: <la4fgtINNhs6@news.bbn.com>
- Sender: usenet@cpu.com (Usenet administrator)
- Organization: Computerized Processes Unlimited, Metairie, LA, (504)-889-2784
- Date: Mon, 31 Aug 1992 19:04:42 GMT
- Message-ID: <1992Aug31.190442.2507@cpu.com>
- Reply-To: gwlester@cpu.com
- Distribution: na
- Lines: 20
-
- In article <la4fgtINNhs6@news.bbn.com>, mjensen@BBN.COM (Martin Jensen) writes:
- > Thank you O Gods of VMS for a prompt and satisfying response to my
- > earlier query!! Now for the next question :-)
- >
- > I'm trying to write an exit handler for a VMS program written in
- > VAX-C. The various VMS manuals have left me a little confused as to
- > the calling conventions for exit handlers.
- >
- > The Programming Resources Guide indicates that the exit handler
- > should be written as a subroutine - implying (in my mind anyway) that
- > the handler is called with a JSB and should return with a RSB. Other
- > documents seem to indicate that the handler is called as a normal
- > procedure - implying (again, in my mind) that the handler is called
- > with a CALL(S,G) and should return with a RET instruction.
- >
-
- It is invoked with CALL(S,G). It should (must?) not return a value.
- Some writters equate subroutine with procedure vs function. While I have never
- written an exit handler in C, I have several in FORTRAN and Pascal.
-
-