RE: Defining a function key...

I prefer renaming indicators to references to the AID byte (via pointer or
INDARA/INFDS). But it's just that--a personal preference. I like to name
attribute indicators so I don't have to keep referring to the display screen
to figure out what happens when *IN41 gets set on. Renaming *IN41
'PC_CustNumber' gives me more clues without needing a separate comment.
Since I want to name attribute indicators, I might as well do the F-keys
that way, too, unless I need them all for attributes. Then the AID byte is
mighty handy. The more tools you have, the easier it is to get the job done.

As for what's simple code--that depends on the education and experience of
the programmer. A survey of shops using INK_ may say it is simple. Those who
don't know pointers think the example below is hard, but people who have
been exposed to it may prefer it. And who knows what education and
experience the next guy will have?

Thank you, IBM, for all the options. But it does make the K.I.S.S. method
more complex to recognize in any given situation.

Roger Mackie

-----Original Message-----
From: dmosley@dancik.com [mailto:dmosley@dancik.com]
Sent: Tuesday, March 19, 2002 7:42 AM
To: rpg400-l@midrange.com
Subject: RE: Defining a function key...



Just curious, but doesn't anybody else RENAME their indicators.
Forget all that AID stuff, and even the *INKx stuff.

 * -- Indicators...
d ind@ptr         s               *   inz(%addr(*in))
d indicators      ds            99    based(ind@ptr)
 * ---- 01 - 29 : Functions Key indicators...
d  f3@exit                        n   overlay(indicators:03)
d  f6@cancel                      n   overlay(indicators:06)
d  f7@exit                        n   overlay(indicators:07)
d  f12@cancel                     n   overlay(indicators:12)
d  pagedown                       n   overlay(indicators:25)
d  help@key                       n   overlay(indicators:29)