RE: General ILE question - *LR

I suppose the first question is why do you want to do this?
What can you possible gain from making a module that has the RPG logic cycle
in it a bound call?
Leave it a stand-alone program and dynamic call, you'll be better off.
The only time you use multiple modules is when the NOMAIN keyword is
specified on the header specification of the secondary modules.
If you haven't begun using subprocedures, don't move to multiple modules.
The "correct" order (in my view) is to begin using subprocedures first, then
move to using multiple modules.  The capability to call a module by name
using CALLB or a prototype is an anomaly due to the way RPG is structured
and should always be avoided.
-Bob Cozzi


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Krish Thirumalai
Sent: Friday, January 07, 2005 10:24 AM
To: RPG programming on the AS400 / iSeries
Subject: General ILE question - *LR

I have a general ILE question.  Say I am creating a module that is
bound by copy to the calling program.  The module has a mainline that
logic will flow through each time it is called.  Do I want to set
*INLR on each time when logic reaches the end of the mainline or
should I always just RETURN?  Does turning on *INLR really do anything
if the program is a module?

Thanks

Krish
-- 
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.