|
In the very same program that I had the do loop I started adding subprocedures. The fellow who wrote the original program will never use a subprocedure and promptly takes them out of code that I modify for him. (Jon, he was the one who ground his own coffee beans for you when you came onsite to teach us RPGLE.) Now, I want to play along, and use his subroutines but I can't because I use subprocedures. So, I end up putting most of the guts of his subroutine into a subprocedure. Now, for another example of why I prefer subprocedures instead of subroutines. In his code I see a lot of (must use MOVE instead of EVAL to thwart any attempts to convert to free form): C MOVE WRKVR1 SUBVR1 C MOVE WRKVR2 SUBVR2 C MOVE WRKVR3 SUBVR3 C MOVE WRKVR4 SUBVR4 C EXSR $SUBR C MOVE SUBVR4 WRKVR4 Avoiding this crud is why we have prototypes, CONST, etc. Rob Berendt
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.