|
Buck, you don't even need the U1. you could just comment out the exsr statement - you're allowed to have subroutines that are never referenced, just not the other way around. just call it the "rainy day module". (write extra code, just in case somebody needs it later) http://www.waterfall2006.com/gorman.html On 10/17/06, Buck <kc2hiz@xxxxxxxxx> wrote:
> Karen: Something we just thought of was: Now, how do you un-comment > these lines when you want to start using the code again? By hand. A different method would have been to insert a different comment, like //*. Then, un-doing it would have been easier. My preference is the compiler define, but a trick I used years ago was to put the block of code in a subroutine and condition the EXSR on an external indicator like NU1. Leave U1 off (i.e. normally) and all the code executes as always. CHGJOB SWS(10000000) then CALL mypgm, and the block of code doesn't run. You can flip it on the fly without re-compiling. --buck -- This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list To post a message email: RPG400-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/rpg400-l or email: RPG400-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/rpg400-l.
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.