Re: Bind by reference doesn't mean dynamic call?

Even the first call to a procedure in a service program isn't dynamic.

"Dynamic" means that the actual program/procedure to call is resolved
from the given name at run-time, which means that the call takes a
little bit longer.

With ILE procedures, all calls are bound calls. Which means the name
resolution is taken care of at compile time (Techinically, the name is
resolved during the second step known as linking.) It doesn't matter
if the code is bound by copy or bound by reference.

There's a small bit of overhead to activate the *SRVPGM the first time
any procedure is called from it, but that time is irrelevant as long
as you don't do something silly like have one procedure per *SRVPGM.

Besides a much improved maintainability, having shared modules in
service program saves space vs. having shared modules bound by copy.

HTH,
Charles


On Tue, Feb 24, 2009 at 9:32 AM, David FOXWELL <David.FOXWELL@xxxxxxxxx> wrote:

Having a problem explaining to colleagues in a world without service programs that using them does not mean dynamic calls and thus poor performance.

If I understand correctly, the first call is akin to being dynamic, but afterwards the link between program and service program is static and therefore as fast as a module bound by copy.

Anyone help me out in simple English?

Thanks
--
This is the RPG programming on the IBM i / System i (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.