RE: ILE Propoganda

["Bill Bynum" <bill.bynum@xxxxxxxxxxxxxxxxxxxxx>]

>I can't tell you the number of times I've heard various junior
>programmers
>say something similar.  How about a more realistic scenario?

In my MANY years of programming,(mind you that MANY constitutes  a level
much higher than Jr. programmer) every subroutine written in programs that
are currently being used in a production environment have been previously
tested(i.e. old code that is NOT broken). Granted, you may have to tweak the
code(i.e. change indicator references, etc.) but it puts the code right in
front of you rather than relying on a hardcopy, and/or an additional
session, swapping back and forth from one to the other.

Talking about being realistic, when you are dealing with RPGII, RPGIII,
RPG400, and RPGLE in one environment, and you know that there is a
subroutine or a piece of code that is being used in an RPGII program that
would help you in an RPG400 program, you better believe that I will go and
copy that code and drop it into the new program. And the nice thing about
it, it works every time.



Bill



-----Original Message-----
From: owner-rpg400-l@midrange.com [mailto:owner-rpg400-l@midrange.com]On
Behalf Of Buck Calabro
Sent: Thursday, June 21, 2001 12:15 PM
To: RPG400-L@midrange.com
Subject: RE: ILE Propoganda


>It seems to me that if it is code that has been
>previously written in another program, the
>simplest and quickest way would be to copy
>and paste that part of the code to the new
>program. Let's face it, for most every project
>you are working on there is a deadline

I can't tell you the number of times I've heard various junior programmers
say something similar.  How about a more realistic scenario?

"copy and paste that part of the code" versus

o Locate the code.  It's everywhere, so decide which version is closest.
o Copy and insert the code.
o Change the field names to fit the new code into the existing program.
o Check the indicators to be sure there's no overlap.
o Doing I/O? Check that we won't disturb the file pointers.
o Manipulating text? Change the array size/field lengths to match the new
requirements.
o Manipulating numbers? Change the field sizes to match the new
requirements.
o Got work fields?  Don't want to miss them.
o Test the new code to see if it works.
o Test the old code to see that it isn't broken.

Integrating at the "copy the source code" level takes more than simply
copying lines of text.  If it truly WERE that simple, wouldn't most of your
code be /COPY statements?

Buck
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator:
david@midrange.com
+---

+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---