Jon,
> I would love to understand how AREAD is so significant.
It comes down to both macro simplicity and usage simplicity.
Code a replacement macro using your method. You will find that macro
will be much more complicated as how it handles the A and
C labels. You now have to use GLBx values
Thanks Tony, This new example demonstrates a valid use for AREAD. It does not
have any executable code and it clearly has benefits over using assembler.
I would love to understand how AREAD is so significant. Is there still anyone
who disagree's with my statement "Never use AREAD unless it's
Jon, I was trying to show a very basic use of AREAD, something so the OP
had something of an example.
Back to the OP's question, where he wanted to build a large table. I
have attached an example of just that using AREAD. It's from one of my
message programs. I have striped out the program
Hi Ed,
You said you highly recommend using AREAD & AINSERT. With their limitations and
restrictions, I'm surprised you could be so unequivocal. Can you show us an
example of a second macro using one an AREAD based macro with the data in that
macro?
After looking at the BRANCH_ON macro, would
Sorry Tony, I was trying (apparently unsuccessfully) not to be insulting.
You recommended to the op that he should consider AREAD. With less than 5% of
macro's being improved by AREAD, what did you notice that AREAD needed to be a
consideration? I'm all for using AREAD when it's needed but
Years ago I suggested the need for an ACOPY statement that would only be
processed if conditional assembly did not bypass it. But I never created a
Share requirement or RFE.
Keith
Sent from an iPhone
> On Mar 8, 2019, at 12:37, Paul Gilmartin
>
RFE?
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List on behalf
of Paul Gilmartin <0014e0e4a59b-dmarc-requ...@listserv.uga.edu>
Sent: Friday, March 8, 2019 2:37 PM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
On 2019-03-08, at 10:06:12, Jonathan Scott wrote:
>
> When AINSERT was invented, about 20 years ago, the HLASM team
> failed to anticipate some of the ingenious ways in which it
> might be used, especially inserting COPY statements ...
>
The need to AINSERT COPY statements is a relic of a
Never use any facility unless it is really needed and you are willing to code
it correctly. AREAD has legitimate uses, and since it is prt of HLASM then
using it is not circumventing the assembler.
"When the only tool you have is a pipe, everything looks like a filter."
--
Shmuel (Seymour J.)
IMHO we all owe a large debt of gratitude to John and Greg.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List on behalf
of Tony Thigpen
Sent: Friday, March 8, 2019 5:22 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Useful, yes. Most powerful - not even close.
--
Shmuel (Seymour J.) Metz
http://mason.gmu.edu/~smetz3
From: IBM Mainframe Assembler List on behalf
of Ed Jaffe
Sent: Friday, March 8, 2019 10:35 AM
To: ASSEMBLER-LIST@LISTSERV.UGA.EDU
Subject: Re: Best
Ref: Your note of Fri, 8 Mar 2019 16:01:45 +
I've used AREAD a lot (for example for in-line message tables
and as a simple way to enable or disable debugging code) and
AINSERT too, especially for some tricks relating to global
variables which couldn't be done any other way.
I feel that it
I'd be okay with that. I'll put together an abstract...
On 3/8/2019 8:01 AM, Farley, Peter x23353 wrote:
Ed,
That sounds like a great topic for a SHARE presentation on advanced assembler
usage, if it's not considered too proprietary to release into the wild.
Any chance of that happening?
Ed,
That sounds like a great topic for a SHARE presentation on advanced assembler
usage, if it's not considered too proprietary to release into the wild.
Any chance of that happening?
Peter
-Original Message-
From: IBM Mainframe Assembler List [mailto:ASSEMBLER-LIST@LISTSERV.UGA.EDU]
I think Jon Perryman's comment deserves a little more respect. Another
famous guy, Albert Einstein, famously said something like keep things as
simple as possible. There's a bad tendency among some to play with any
shiny new tool they find, regardless of whether it's actually appropriate
for the
On 3/7/2019 8:54 PM, Jon Perryman wrote:
Never use AREAD unless it's really needed and you are willing to code it
correctly. Circumventing the assembler is not helpful.
AREAD/AINSERT is arguably the most powerful single mechanism in all of
HLASM. We use it *everywhere* to build tables and
I wish I still had those emails.
John was very helpful to me back around Y2K with suggestions on how to
use the advanced features of HLASM to make my life easier. *ALL* my
knowledge of writing macros comes from his tutelage and reading his
three 'how to' guides.
Tony Thigpen
Martin
Pardon me for jumping in-
>> considering that the one that told me to use AREAD,
IMNSHO the question is as important as the answer!
Martin
So, your statement comes down to "Don't use AREAD because it's not HLASM."
Considering that the one that told me to use AREAD, including providing
the base examples, was John Ehrman, I think I will take his opinion over
yours.
I said this was a simple version. Some of my more complex ones
19 matches
Mail list logo
