Robert Rosenberg wrote
>Why not just multi-path logic? You pass a flag for the scope in pass_scope
>as 0=SINGLE, 4=ALL, 8=COMMON and go:
I actually use a similiar logic now, I was trying to get a single routine and
once instance of the macro.
-- Original Message --
From: "Robert
I prefer to determine the SCOPE specification at execution time.
-- Original Message --
From: John Gilmore
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: DSPSERV with SCOPE=?
Date: Sat, 9 Feb 2013 15:40:37 -0500
The obvious question is that of the binding time of this requireme
For execution-time binding Robert Rosenberg's scheme, or something
very like it, is the only viable one. (I looked at the macro
definition.)
John Gilmore, Ashland, MA 01721 - USA
The only supported approach to parameterize the SCOPE value at runtime is
brute force,
in your case triple-pathing the code for the three choices you want to
make available.
Peter Relson
z/OS Core Technology Design
At 08:43 -0500 on 02/10/2013, John Gilmore wrote about Re: DSPSERV
with SCOPE=?:
For execution-time binding Robert Rosenberg's scheme, or something
very like it, is the only viable one. (I looked at the macro
definition.)
John Gilmore, Ashland, MA 01721 - USA
At 10:01 -0500 on 02/10/2013, Pe
At 12:34 + on 02/10/2013, esst...@juno.com wrote about Re:
DSPSERV with SCOPE=?:
Robert Rosenberg wrote
Why not just multi-path logic? You pass a flag for the scope in pass_scope
as 0=SINGLE, 4=ALL, 8=COMMON and go:
I actually use a similiar logic now, I was trying to get a single
routine
Things like that---It is a sort of COBOL ALTER---can be done; but the
result is not reentrant, would be hard to maintain (collateral changes
would be required every time IBM changed the macro's code skeletons),
etc., etc.
Á chacun son goût.
John Gilmore, Ashland, MA 01721 - USA
