RE: More on RPG style

These two items that are up to interpretation.

So you know, it is generally considered bad form to issue RETURN before

the

ends of the procedures/functions in which they appear. Put another

way,

Return should appear only as the last statement of a procedure. If it

is

later determined that this procedure musty return a variable, how many
(otherwise unrelated) changes will need to be made in order to support

that?

In general I would agree with you. But, when you are performing
multiple tests
and as soon as you fail the first one, it is generally acceptable to
return immediately.

There is little use to clutter up a procedure with multiple ifs, ands,
endifs, etc.

It is also considered bad form to use the word NOT where avoidable.

How

much clearer would your code appear if it said:

Some clients prefer 'Not =' to '<>'.
Not equal is only one logical test where '<>' is two logical tests.
Besides it is much easier to debug 'not =' vs '<>' when the previous
pgmr
Simply "forgot" half of the operand.

Generic approaches to coding style are always open to interpretation.
The world
is not a one size fits all.