home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!destroyer!cs.ubc.ca!van-bc!panam!emma!rick
- From: rick@emma.panam.wimsey.bc.ca (Rick Younie)
- Newsgroups: comp.lang.rexx
- Subject: SIGNAL ON Helpme
- Message-ID: <oylXr*he1@emma.panam.wimsey.bc.ca>
- Date: Fri, 06 Nov 1992 05:52:24 GMT
- Distribution: world
- Bcc: rick
- X-Newsreader: Arn V1.00 beta rel2
- Lines: 28
-
- I've started appending an error trapping routine to my scripts, using most of
- the SIGNAL ON options. The routine writes an entry in the system log when a
- script fails and also pulls the offending script into the text editor and
- positions the cursor on the line with the error.
-
- This routine would be a perfect candidate for a subroutine if I could figure
- out a way to do it.
-
- Have I got this right? The SIGNAL instructions and the subroutines that they
- point to must be in the base script (what is the proper name for this
- anyway?). So neither can be in an external subroutine. It's not even
- possible to have this set-up routine as an internal subroutine, is it? Then
- it could be tacked on the end of the script instead of messing up the start.
-
- I thought of one way to do it, but it is fairly mickeymouse. ARexx can
- invoke scripts asynchronously, so a script could call the setup routine and
- then exit. The setup routine would then call it back in turn, passing back
- the original parameters and also a flag so a loop wouldn't be set up. I'm
- not sure I've explained this clearly..
-
- Is there an easier way to do this?
-
- Rick
- --
- ------,------
- rick@emma.panam.wimsey.bc.ca | 1:153/765.9
- rick@emma.tfbbs.wimsey.bc.ca | 1:153/911
- ------'------
-