|
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). ----- Original Message ----- From: "James W. Kilgore" <qappdsn@attglobal.net> To: <RPG400-L@midrange.com> Sent: Tuesday, May 09, 2000 11:53 AM Subject: Re: RPT vs RPG > With RPT you can use /COPY members that contain multiple source types and they > will be automatically sorted into their proper sequence. > > /COPY for RPGLE does not do this. > > For example, in RPG/400 we have a /COPY for each file that contained the key list > ('C' spec) and data structures ("I" spec) and by specifying RPT as the source > type, the 'I' and 'C' specs would be put in their proper place. > > Since RPGLE is the way to go, we created two /COPY members, one with the key list > ('C' spec) and one with the data structures ('D' specs) and put the /COPY > statements at the point in the program where the code belongs. > > HTH > > Khouw Thiam Hok wrote: > > > Hi, > > Can anyone explain RPT vs RPT differences ( when to apply, advantage and > > disadvantage). > > +--- > | 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 > +--- > +--- | 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.