× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. RPG400-L
  3. February 2005

Re: Externalizing I/O was RPG read loops

On Wed, 2 Feb 2005 rob@xxxxxxxxx wrote:

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.

Even though we don't use getters and setters here at my shop (though I'm thinking about it) we end up doing the second thing you describe most of the time anyway. Consider:

chain filename
eval  screenfield1 = dbfield1
eval  screenfield2 = dbfield2
...
// most work is done with screen fields

We work this way so that users can opt to discard the changes they have made. Plus it is easy for us to tell what they have changed. Plus other good things. So having getters and setters wouldn't increase the amount of coding in this situation.

James Rich

It's not the software that's free; it's you.
        - billyskank on Groklaw

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.