Re: New to RPG

There is a big difference in using /copy to copy code and using /copy to
copy interfaces to service programs and dynamic called programs.

The first sucks, the second should be mandatory.

About rewriting code, hmm, if you use a generic low level module that
dosn't require
changes there is no need to rewrite it. If you are going to make major
changes
it should be considered.

On Sun, Apr 30, 2017 at 3:10 PM, Buck Calabro <kc2hiz@xxxxxxxxx> wrote:

On 30 April 2017 at 01:58, D*B <dieter.bender@xxxxxxxxxxxx> wrote:

the main problem is: who is using all the nice possibilities of modern
RPG!!! Even using totally free lots of programms are written in a style,
thinking in punching cards: large monolithic programms, right hand side
comments, moving *ON to *INLR, using available components (I'm providing
some fro free) by copiing to the own monoliths, trying to use binder
language (without understanding how it works) to avoid rebinding-

I agree with your assessment, but I especially agree with this.

Copying code without understanding it is killing us.
If we understood it, we'd never copy it -- we'd write better.
Not because the code is old per se, but because that pattern is no
longer the best fit to the problems it is being twisted into solving.
--buck
--
This is the RPG programming on the IBM i (AS/400 and iSeries) (RPG400-L)
mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD