Re: File Read in Subprocedure WAS(Re: More on RPG style)

I tend to favor the "business objects" approach.

For example - I might
want to retrieve the shipping address - I sure as heck don't want to
implement that as a series of getter requests - yuck!

...even the most hardened of OO bigots seem to have moved away
from the "Thou shalt always have a
getter and setter for every column in thy database" silliness.

Pardon my ignorance, but not sure I follow completely. I know this is an
RPG list so forgive me for talking PHP for a moment...

I usually only have setters and getters for every field in PHP because I
use a component to generate the object, but I certainly add "getters" to
format data in a more relevant way. For instance, there might be a
getShippingAddress that puts the full address together from several fields.
On the setter side, I might code a setShippingAddress that breaks the
address into its individual components and sets the appropriate database
fields.

Is this the kind of strategy you are talking about or something more
involved?