RE: Defining a function key...

Denis,

uh, you know, I can't remember the last time I wrote an RPG program and
thought to myself...

"Hmmm... I wonder if a C programmer would understand this section of code.
Maybe I aught to make my RPG look as much like C as possible, so that in
case someone who only knows C want's to change it, then he'll be able to."

But now I'm leaving out all those COBOLers.  Maybe I should write it so
that it would be better understood by COBOL programmers.

I don't mean to be curt, but I write rpg programs clear enough so that rpg
programmers can change them.  I don't care if a C programmer has to learn a
few basic rules of my preferred language.

Rick

---part of the original post---
For a C or JAVA programmer, I have no doubts as of which of the following
is
the easiest to interpret:

if   *inkc
eval  *inlr = *on
endif

{The C guy thinks: *inkc must be a boolean variable, but what does it
stands
for? it is not defined anywhere!!! ok now, if the condition is true, then
set
the boolean variable *inlr (what the hell does inlr mean) to true. But
wait,
that *inlr variable is not reference anywhere!! it must be dead code and I
could just remove it}