|
Nelson, When we went from RPG/400 to RPGLE and had to deal with the /COPY issue we tossed a coin. Since we have to touch every program, the decision came done to: do we use the compiler directives or just break apart the /COPY members. The coin came up: break them apart. Not that either decision is better/worse than the other, it still boils down to having to make a manual change to every program that uses the /COPY member. Since ILE can't sort them out by itself, and ILE is the future, IMHO, /COPY with only what you want, placed where you want it, is a guess as to tomorrow's lost "features". Sort of like getting it all to work with sqlRPGLE. "Nelson C. Smith" wrote: > Using the Define/Undefine compiler directives will let you keep all your > different line types in the same source member and copy in only what you > want, where you want it. In fact, I have one source member, called > IncludeSrc, that contains everything from single lines to code snippets, to > entire programs. In the target program, I just define the portions I want, > at the location where it should go, and everything works fine (until you try > it with that dratted SQLRPGLE precompiler, that is). > +--- | This is the RPG/400 Mailing List! | To submit a new message, send your mail to RPG400-L@midrange.com. | To subscribe to this list send email to RPG400-L-SUB@midrange.com. | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.