Re: Pointer puzzle

It really depends on the situation an application (PGMs, SRVPGMs, etc)
have to be used. If you are writing for data to the Web you want to limit
the interaction between client and server, so passing arrays is a viable
solution. Performance is another issue.

What kind of design model are you thinking of? MCV: don't think so.

And please, define "monolith"?

And I thought pointers could only be defined in RPG IV, so why coding in
RPG IV is monolith and using the ILE concept is not? (Sub)procedures), like
subroutines in the old days, were implemented on functionality and (logic)
programme structure.

Old wine, new bags. Or another dead horse resurrected.

With regards,
Carel Teijgeler


*********** REPLY SEPARATOR ***********

On 5-10-2009 at 19:00 Alan Campin wrote:

Why not write a ILE program instead of monolith? Loading in array or huge

structures or even passing a pointer is monolith.

In ILE you have a service program with multiple functions. One function

loads the data and stores it. If it is a lot I use a user space. The

function returns a count of records found.

A second function reads records in a loop returning one record or piece of

information at a time.

This is the whole idea behind ILE. Small procedures that run really fast

each doing one thing and then you are not doing horrible things like pass

pointers to storage or returning array, etc, etc.