Re: Ignoring a RETURN'ed value

["Keith Carpenter" <CarpCon@xxxxxxx>]

Nope.
It will work just fine.

The compiler will list a RNF5409 warning message that the return value will
be lost.

Keith


----- Original Message ----- 
From: "ile rpg" <ile_rpg_guy@xxxxxxxxxxx>
To: <rpg400-l@xxxxxxxxxxxx>
Sent: Friday, March 19, 2004 3:57 PM
Subject: Ignoring a RETURN'ed value


>    I have a frequently-used pop-up which currently has two parameters: one
>    input, the second output.
>
>    I'm going to refactor the program to RETURN the value.  But I don't
want
>    to change the thousands of places it's used in hundreds of programs.
Yes,
>    I could write a new program, but I donwanna.
>
>    My plan is to add a return value to the protoype, RETURN the value,
>    and handle parameter 2 as *NOPASS: if it's there, I'll return a value
in
>    parameter 2; otherwise I'll ignore it.
>
>    The question: if I have a return field specified in the prototype but
do a
>    CALLP  {program}(parm1: parm2) instead of doing EVAL {result} =
>    {program}(parm1), will there be h^ll (with a nod to the SMEX luddites)
to
>    pay?
>
>    thanks,
>    IRG
>
>      ---------------------------------------------------------------------
-
>
>    Find a broadband plan that fits. Great local deals on high-speed
Internet
>    access.
> _______________________________________________
> 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.
>
>