RE: /FREE RPG compiler errors

["Joe Pluta" <joepluta@xxxxxxxxxxxxxxxxx>]

> From: Barbara Morris
>
> Joe, that's true in V5R1.  But V5R2 added a couple of features that are
> only available in /free:
>
>    chain %kds(mykeys) rec;     // use keyfields defined in D specs
>    chain (k1 : 'A') rec;       // list keyfields directly
>    dsply ('fld1 = ' + fld1);   // dsply an expression

Oh no.  Argh.  Now you put me in a tough position, Barbara!  Those are very
cool opcodes, and yet more reasons to like /free, but they're not available
to my RPG IV programmers (and why not, I guess I'd ask, but that's a
different topic).

Okay, let me put a hypothetical to you.

Let's say you had a 20,000 line program (I know this is bad to start with,
but this is reality) and it had roughly 500 MOVE opcodes in it.  This is not
an unusual circumstance in any legacy shop.  For some reason, we had an
"opportunity" (and I use the term loosely) to add a new file for some sort
of lookup operation.

Would you (and remember, death is not an option):

1. Pass on /free and add a KLIST and the appropriate chains
2. Toss in a block of /free code to make use of the new chain syntax
3. Rewrite the entire thing removing the MOVE opcodes

This is not a test.  There are no right or wrong answers, just your opinion.
Whether I agree or disagree, I am honestly curious as to what you folks
working on the compiler think we should do, those of us with legacy systems
to maintain.

Bonus question <grin>: Would the fact that there are 20 or more programs
like this make a difference?

Joe