I just took a closer look at page 56 of the presentation. Based on what
I see, I will never want to use FLOWASM. Here is the output from two
adjacent lines:
.0000329A 95F2 A00B 0000000B 58559 ¦ : IF CLI,EMRJES,EQ,EMRJES2
.000032A2 5810 C4F4 0000353C 58573 ¦ : | L R1,=A(J2TDFLDIDX)
Instructions 329E thought 32A1 are hidden. I can handle hidden
instructions in system macros, but not in, what I would consider, open
code where I may have fat-fingered something. I guess I rely too much on
looking at the generated code when debugging.
To each his own.
Tony Thigpen
-----Original Message -----
From: Ed Jaffe
Sent: 12/04/2013 05:45 PM
On 12/4/2013 1:37 PM, Tony Harminc wrote:
Well, sure, but all the ugly generated labels and such are there when
you have to read the listing rather than the source. And there are
times when you have the offset where something program checked, and
the source just won't do.
We use FLOWASM. Therefore, most listings we read look like what's
pictured on slide 56 of this SHARE presentation:
ftp://phoenixsoftware.com/pub/demo/Structured_Assembler.pdf
--
Edward E Jaffe
Phoenix Software International, Inc
831 Parkview Drive North
El Segundo, CA 90245
http://www.phoenixsoftware.com/
