RE: Large Return values (was Re: Variable Length Field Question)

Brad,
I recently went through my RPG ToolKit (www.rpgiv.com/toolkit) code and
replaced my TOUPPER() function which returned a VARYING parm that was 32k in
length, with a CvtCaseEx(InValue:OutValue:%len(OutValue)) call.
I also created a CvtCasePtr() that does the same thing, except it requires
%addr() for the first two parms. But I don't use it unless I'm passing in a
VARYING field since if you remove CONST from the parm, you loose the "auto
casting" from VARYING to fixed-length or vice versa. 
Not only did this cut down on resource utilization, it also improved
performance substantially throughout the entire set of procedures.
-Bob Cozzi


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of Brad Stone
Sent: Thursday, May 20, 2004 7:47 AM
To: RPG programming on the AS400 / iSeries
Subject: Large Return values (was Re: Variable Length Field Question)

Ya, I've heard about this as well.  Is the suggestion then
to return pointers?  Does this also apply to passing
parameters that are large values, or just returning large
values?

Brad

On Thu, 20 May 2004 11:48:34 +1200
 "Peter Connell" <Peter.Connell@xxxxxxxxxxxxxxxxxxxx>
wrote:
> Brad,
> A warning on large variable length return values.
> 
> Previous responses I've had on this list by the IBM guys
> indicate that
> it appears the compiler has not been designed to
> accommodate these as
> well as might be hoped.
_______________________________________________
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.