RE: Odd CALLPRC behavior when using RPG indicator with RTNVAL

The only problem with EXTPROC(*CL) is that it changes the way the
procedure handles the return value under the cover. So if you are
modifying an existing RPG routine, you'll have to recompile all callers
for them to work.

That's it! I knew there was some issue but couldn't remember the details.
Too many things going on today I guess.

--
Jeff Crosby
UniPro FoodService/Dilgard
P.O. Box 13369
Ft. Wayne, IN 46868-3369
260-422-7531
www.dilgardfoods.com

The opinions expressed are my own and not necessarily the opinion of my
company.  Unless I say so.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of Scott Klement
Sent: Thursday, March 12, 2009 3:17 PM
To: Midrange Systems Technical Discussion
Subject: Re: Odd CALLPRC behavior when using RPG indicator with RTNVAL

Hi Jeff,

IOW (correct me if I'm wrong), one cannot define a parm in an RPG

program

as

type N and be able to call that RPG program from both CL and RPG. If

you

want to call it from both CL and RPG, define the parm as 1A.

No, that's not true. First of all, there's no difference between 1N and
1A -- they both exhibit the same problem.

Second, if you code EXTPROC(*CL) it will work from both RPG and CL.

The only problem with EXTPROC(*CL) is that it changes the way the
procedure handles the return value under the cover. So if you are
modifying an existing RPG routine, you'll have to recompile all callers
for them to work.

If you're writing a new routine, this isn't a problem. It's only when
adding EXTPROC(*CL) to a routine that previous didn't have EXTPROC(*CL).

But, once added, it will work properly from both RPG and CL.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.