Re: Dynamic Array as return/output parameter in export procedure

AFAIK, in the variable section of ibm api, the caller is still making
the decision of telling the api how much data it should generate. The
only exception I can think of are api data return data to the user
space.

As mentioned, in my situation, the procedure is likely to only generate
one to two elems in the output array. But to make sure I handle special
situation where thousands of elems could get returned from the
procedure, I decided to make this output array as big as I can. Since,
in most case, it only generate one or two elems, my initial reaction is
to make it a dyna array. But from Scott's reply, it seems like that is
not very necessary. So..., I just curious as when would dyna array
become appropriate.




<vhamberg@xxxxxxxxxxx> wrote in message
news:<mailman.12159.1221921208.2545.rpg400-l@xxxxxxxxxxxx>...

Lim

Scott did say that the technique applies when things are sufficiently

complex - an example in my mind is the variable sections returned from
APIs - where in fact one doesn't even have to necessarily allocate space
in the caller - the callee allocates it and then tells the caller in
various ways how much is allocated - things like number of entries,
length stuff, offsets in the fixed part, etc.

I think that typically those who write business apps, not APIs, are

not usually doing really complicated stuff. The KISS principle applies -
Keep It Simple (fill in your favorite S-word).

Vern
-------------- Original message --------------
From: "Lim Hock-Chai" <Lim.Hock-Chai@xxxxxxxxxxxxxxx>

Is statement below apply to all situations or depends?

"Scott Klement" wrote in message
news:...

But would rather that he stop using this technique altogether :)

--
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.