Re: REXX Problem
- From: gilmap@xxxxxxxxxxxx
- Date: 17 Jan 2006 16:40:40 -0800
In a recent note, Rob Scott said:
> Date: Tue, 17 Jan 2006 17:27:42 -0500
>
> "Note: once you execute "address ISREDIT", there is no need to put
> "ISREDIT" in front of every command."
>
> Maybe not - but I think it is good practice - it protects you from
> problems if you happen to ADDRESS another environment when you next
> change the REXX exec. Admittedly this might not be a big issue with
> simple edit macros - but in larger REXX execs you can easily shoot
> yourself in the foot.
>
> I also think that it makes the code easier on the eye and easier to
> maintain.
>
You could make the same argument for putting a USING or a CSECT
in front of every other assembly language statement.
And it wouldn't be true there, either.
(Although HLASM reports effective USINGs at the top of each page.)
And, following up on teD's reasoning, if I have a large
chunk of statements in another environment, I'll habitually
make a PROCEDURE out of it. Since the previous addressing
environment is restored on return, everything desired
happens automatically.
No, I don't put a restoring ADDRESS ... either before the
RETURN or after the CALL (although Ed Jaffe might like it
that way.)
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to listserv@xxxxxxxxxxx with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
.
- Follow-Ups:
- Re: REXX Problem
- From: Edward E. Jaffe
- Re: REXX Problem
- Prev by Date: RE: Migration to Shark
- Next by Date: Re: Does DDNAME=? override SUBSYS=?
- Previous by thread: Re: REXX Problem
- Next by thread: Re: REXX Problem
- Index(es):
Relevant Pages
|
