Re: Max number of Parma on a prototype

No, using a large number of parameters would point to a design error. If
IWS takes a XML document and creates a parameter for every XML element,
sounds like it is a design error. That is stupid in my opinion. You know
you are going to have XML documents with more than 500 elements. The only
solution they can come up with is to pass the XML document by one parameter
for each XML element? .


On Tue, Oct 8, 2013 at 3:18 PM, John Yeung <gallium.arsenide@xxxxxxxxx>wrote:

On Oct 8, 2013, at 1:31 PM, Alan Campin <alan0307d@xxxxxxxxx> wrote:

Why would you
ever code a procedure to have that many parameters?

On Tue, Oct 8, 2013 at 3:50 PM, Rpglist <rpglist@xxxxxxxxxxx> wrote:

I was testing the iws today and it appears that for every inbound
XML or soap field I need a Parm defined on the PR and ladies
and gentleman my XML will have in excess of 500 elements

Hm. I wonder which one of the several male readers on this list is
the gentleman. ;)

I think Alan was incredulous about coming anywhere near the maximum
because, since before the dinosaurs, whenever any piece of code needs
more than two large, heaping handfuls of parameters, it's time to
bundle them all up and pass them as a single parameter (possibly a
pointer, depending on the call interface), which is then chopped up or
parsed as needed.

John
--
This is the RPG programming on the IBM i (AS/400 and 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.