home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cis.ohio-state.edu!sample.eng.ohio-state.edu!purdue!yuma!csn!stortek!LSTC2VM.stortek.com!GILMART
- From: GILMART@LSTC2VM.stortek.com (Paul Gilmartin)
- Newsgroups: comp.lang.rexx
- Subject: Re: NOVALUE (was: Blanks, REXX, and portability...)
- Message-ID: <16860347.GILMART@LSTC2VM.stortek.com>
- Date: 12 Sep 92 06:13:53 GMT
- References: <mwm.1udh@contessa.palo-alto.ca.us> <19920910194427SEB1525@MVS.draper.com>
- Sender: usenet@stortek.com
- Organization: StorageTek SW Engineering
- Lines: 15
-
- In article <19920910194427SEB1525@MVS.draper.com>
- SEB1525@MVS.draper.com (Steve Bacher) writes:
-
- >If you use SIGNAL ON NOVALUE, you won't have to put up with this.
- >IMHO, REXX programmers should *always* use SIGNAL ON NOVALUE unless
- >there is a very good reason (obscure hacks included) not to do so.
-
- Ah, but they're making it hard for us! Compiled Rexx and uni-REXX (perhaps
- others) report SIGNAL ON NOVALUE as a syntax error _prior_to_execution_
- if the NOVALUE: procedure doesn't exist. And if I supply the NOVALUE:
- procedure, 370 interpreted Rexx doesn't give the nice call traceback that's
- so precious for debugging.
-
- Sigh,
- gil
-