|
>My point is there's no reason to have to. [flip from /free to fixed and back]. > >MYKEY1 CHAIN MYFILE1 > IF %FOUND(MYFILE1) > MOVE DBFLD1 WKFLD1 > ENDIF > MOVEL WKFLD1 OUTFLD > >It becomes this: > >/free > chain mykey1 myfile1; > if %found(myfile1); >/end-free > MOVE DBFLD1 WKFLD1 >/free > endif; >/end-free > MOVEL DBFLD1 OUTFLD > >You think this makes sense. 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. >I think the requirement of a mixed-mode is an >unnecessary burden I just figured that if a dinosaur like me can use it, it can't be that hard! Although, I don't mix it up quite as much as the above example does... I tend to keep whole sections in one syntax or the other. Like my SQL. --buck
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.