hhhhmmmm.
Jon:
Do you mean it would been treated as extProc('PROGRAM')? If it is
treated as extpgm('PROGRAM'), that would be a dynamic call.
From Emily's email, I don't believe there is a procedure call "program"
in PROGRAM module at all. Even if there is, that is not the one that
the caller will be executing. It will only execute the main procedure
of "PROGRAM" module. This is based on the fact the a module cannot have
a export procedure with name same as module name.
-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Jon Paris
Sent: Friday, April 25, 2008 12:33 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: Re: Prototyped call question?
On 25-Apr-08, at 1:00 PM, rpg400-l-request@xxxxxxxxxxxx wrote:
Thanks for the responses. I'm new at this (ILE not RPG). I think I
understand more clearly now. There was a binding directory in the H
specs. I looked at it, and within one of the bound modules 'program'
was defined as a subprocedure.
There were two giveaways. The absence of an ExtPgm keyword on the
prototype means that the compiler defaults to ExtProc - this cannot be
overridden. In fact it would have been treated as ExtPgm
('PROGRAM'). The second was the N definition for the return value.
_Only_ a bound procedure can return a value. *PGMs can only "return"
data via the parameters.
I would strongly suggest changing the name of the dang thing - giving a
procedure the name of "program" is - to put it politely - just plain
silly and as you now know - it is the kind of silliness that can waste
hours!
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
--
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.
midrange.com
