|
Any modernized qsysinc includes would have to be set up so they defaulted to the old version of the definitions. Even if people were at a release that supported QUALIFIED, they shouldn't have to change all their programs to match the new qualified version of the definitions with the nice subfield names.
Shrug... ship QSYSINC with different source files for each version. If I have (for example):
/copy QSYSINC/RPGLEV4R5,QP0LSTDIThen the definitions in the RPGLEV4R5 source file can be frozen at V4R5. If I want to re-write it to use the newer features in V5R1 (which is the release that has the biggest impact on this sort of thing) then I can re-do the code and use:
/copy QSYSINC/RPGLEV5R1,QP0LSTDIAll they need to do is copy the file with each release, and upgrade the code as appropriate.
Presumably you'd have to /define something to pick up the new version.
Sorry, but... YUCK. I hate having to do a /define before using /copy... that's not elegant at all! After a few releases the tangled mess of /defines and /if defined and /elses would make this code nearly impossible to follow.
What I don't understand is that IBM has been writing these types of prototype members for C since time out of mind. Not just IBM, either! Virtually everyone who provides software aimed at the C developer provides include files, and manages to keep them working from release to release. Why can't IBM do it with RPG? The same capabilities are all there now.
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
