|
> From: bmorris@ca.ibm.com > > If I understand you correctly, you generate new RPG source. If the RPG > compiler ever did change how it handles the indicators, you'd have to > regenerate the source to make the correction, right? (That is, the > indicator > moving stuff is done in the RPG source, not in your routine.) Exactly. But since I already do the 24-move bit for RPG400, it would be no problem to fix the RPGIV generator to do the same thing. I just try to find ways to reduce code bloat, is all, even on generated code (in fact, especially on generated code, since the user has less control over it). Thanks for your insights. So far, the based-array MOVEA works fine, I just thought I'd run it past you to see if I wasn't doing something really dangerous. Joe
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.