Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!snorkelwacker!usc!wuarchive!texbell!merch!spudge!johnm
From: johnm@spudge.UUCP (John Munsch)
Newsgroups: comp.lang.rexx
Subject: AREXX error trapping question
Message-ID: <10020@spudge.UUCP>
Date: 31 Jan 90 18:08:12 GMT
Reply-To: johnm@spudge.UUCP (John Munsch)
Organization: Friends of Guru Bob
Lines: 23

I have an AREXX script where I call a function that sometimes returns an error
value.  So, I put in:

signal on error
	.
	.
	.

error:
	<Error code>
	return

to handle this error value.  Great so far.  But when I attempt to "return"
from the error handler it treats the "return" as an exit.  I read in the
manual that this is what happens whenever you perform a "return" without
having been "call"ed.  So if I can't return to the point where the error
occurred after having fixed up the problem, what kind of error recovery can
I really have?

John Munsch

P.S.  Every example of error trapping that I've found so far (including those
that came with AREXX) just exit out at the end of the error routine.