|
> From: Buck Calabro
>
> No, I'd argue that this was changed into /free just for kicks.
> Why did the
> programmer change that code? What enhancement was being made? If I were
> doing that and had to have that code in the middle of some new function,
> it'd be using expressions and not MOVE.
Did you finish reading the post? The idea was to use %KDS, Buck, so I was
forced to use /free. That's my whole point. I have to use /free to get the
new stuff, so now I have to switch modes. And your answer is that if a MOVE
is in the middle of some /free code, you'd change it to evals, right?
Anyway, just so we're clear, in order to take advantage of key data
structures, you think this is good:
/free
chain %kds(mykey1) myfile1;
/end-free
IF %FOUND(MYFILE1)
MOVE DBFLD1 WKFLD1
ENDIF
MOVEL WKFLD1 OUTFLD
or alternately (assuming outfld is 10A and wkfld1 is 3P0):
/free
chain mykey1 myfile1;
if %found(myfile1);
wkfld1 = dbfld1;
endif;
%subst(outfld:8:3) = %editc(wkfld1:'X');
/end-free
If so, we have two different opinions of "good", Buck. If, on the other
hand, you say it's "good enough", I say no it's not, because with a little
bit of help, it could easily be all fixed or all free without having to work
in the arcane %subst and %editc syntax.
Joe
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.