|
Anybody have a cheat sheet for 3-to-4 conversions?
In all seriousness, I don't convert RPGIII code other than run it through the IBM conversion (format only.) I leave the MOVEs, Z-ADDs, MULTS and so on just the way they are.
Without analysing every line of code to see if truncations are a desirable side effect or not, it simply isn't worth changing MOVE or MULT to EVAL, especially in the monster programs you're talking about.
I write my NEW code as subprocedures, etc. with new syntax and so on. It isn't at all unusual to write code like this:
EXFMT MOVE MOVE X IFGT Y if checkCredit(cust#: region) = POOR ...original code... endif ENDIFA lot of people have commented that this is ugly. Oh, well. It is what it is. It also works flawlessly, and I can readily insert my changes into existing code without having to worry about the side effects. As a life long maintenance programmer, I've had to look at all sorts of stuff, and my current ideal of 'beauty' involves:
works as desired the first time easy to understand easy to debug easy to change in the future --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.
midrange.com
