|
What you "should" do is to prototype the call to the program and then use the prototype to call the program and not worry about placing it into a subprocedure or a subroutine. You don't place the call anywhere except where you need it. -Bob Cozzi www.RPGxTools.com RPG xTools - Enjoy programming again. -----Original Message----- From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Tony Carolla Sent: Tuesday, December 27, 2005 4:38 PM To: RPG programming on the AS400 / iSeries Subject: Re: CALL In terms of run-time efficiency, I don't believe that placing the call in a subroutine is more efficient. In terms of making the code more readable and modifiable, it is very desirable. For example, what if the program that gets called has a new name someday? Easier to change it in one place. Beyond that, you might use a subprocedure instead of a subroutine, but if the only thing that is happening is a call, a subprocedure might be overkill. I always use subprocedures instead of subroutines, but that is a matter of policy. On 12/27/05, Henza, Guy <GHenza@xxxxxxxxx> wrote: > > I have a program that is calling another program nine times in the > source code. I was taught that when calling the same program multiple > times it was more efficient to put it in a subroutine. Is this correct? > > TIA, > > Guy > > > -- > 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. > > -- "Enter any 11-digit prime number to continue..." "In Hebrew SQL, how do you use right() and left()?..." - Random Thought "If all you have is a hammer, all your problems begin to look like nails"
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.