RE: [RPGNext] Updsrvpgm & file encap.

["Richard Rothe" <RichardRothe@xxxxxxxxxxxxxxxxx>]

I have mentioned all of those benefits.  Not to mention every time
someone clones a program or a piece of code that does what they need, it
creates that much more code to maintain !  Not so with ILE and
procedures.

And, while they agree, they don't know that the time can be spent doing
it.  My boss says go ahead and just do what I need for my current
project and we'll see if we can do more incrementally.    

-----Original Message-----
From: Joel Cochran [mailto:jrc@xxxxxxxxxx] 
Sent: Friday, September 10, 2004 12:00 PM
To: RPGNext Discussion and Information
Subject: RE: [RPGNext] Updsrvpgm & file encap.


On Fri, 2004-09-10 at 20:21, Richard Rothe wrote:
> I've showed my code to the other programmers here and they complained 
> that they had to do a getRecord and then multiple getField evals to 
> get the data they wanted.  "We only have to do one chain and all of 
> the data is there they way we do things now", is what I'm hearing.

And another thing, you are hiding the field implementation!  We've all
seen files with field name like "B5GRZRTS".  It's great if you know the
field name means "Grazing Rights", but how intuitive is that?  Wouldn't
it be better down the road to read code that referred to
"landRights_getGrazingRights()"?  I think new programmers would catch on
a lot faster.

And if you wanted to enforce ALLUPPERCASE for that field, but maybe you
receive it from outside sources, such as text files, and e-mails. 
Instead of needing to remember that the field is *supposed* to be
ALLUPPERCASE in all the calling instances, add the enforcement to the
setGrazingRights() procedure!  One addition and database integrity is
improved.  All while simplifying the long term programming requirements.

I agree with Aaron, you have to look at the ROI.  For me, in a small
shop, the extra time up front will pay off tremendously in the long
term.

Joel
http://www.rpgnext.com


_______________________________________________
This is the RPGNext Discussion and Information (RPGNext) mailing list To
post a message email: RPGNext@xxxxxxxxxxxx To subscribe, unsubscribe, or
change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpgnext
or email: RPGNext-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpgnext.