RE: Externalizing I/O was RPG read loops

["Fisher, Don" <Dfisher@xxxxxxxxxxxxxxxxx>]

I used to think the same way.  It took me quite a while to understand the
benefits of such functions. 

I've been experimenting with them here and have used them to make my file
updates, writes, deletes, etc. exist in only one place.  The same logic to
perform these functions is executed each time one of these operations is
requested.  It gives me the ability to enforce business rules and have only
one place to maintain the logic.

The case for procedures that merely return the data is more difficult,
except I've found these procedures integrate well with the update and record
creation procedures.

Donald R. Fisher, III
Project Manager
Roomstore Furniture Company
(804) 784-7600 extension 2124
DFisher@xxxxxxxxxxxxx


<clip>
I think you're the first person that I heard of, that wasn't the person in
charge of writing the access programs, that actually liked this scenario. 
Why an end developer would like to replace

chain(e) myfile;
// now actually do some real work with the fields

with
getFilename();
MyWorkField1=GetField(field1);
MyWorkField2=GetField(field2);
...
// now actually do some real work with the fields

rather escapes me.
<clip>