× 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.


  • Subject: RE: ILE Propaganda
  • From: "Bartell, Aaron L. (TC)" <ALBartell@xxxxxxxxxxxxxx>
  • Date: Thu, 21 Jun 2001 17:13:04 -0500

I agree with Buck.  If you don't have time to do it right the first time you
will have to make a lot more time to fix it later.

ILE is great and I wouldn't trade it for anything.  I was skeptical at first
but once I started using it I found more and more ways that it just made my
job easier.  The only thing that has gotten me into trouble is signatures,
but once you understand how they work and what not to change in a service
pgm it is not that bad.

ILE in RPG is a great way to prepare you for Java.  Not saying that Java is
what we are all heading to but with the ability to easily call a Java pgm in
V5R1 I can say that I will be making some use of Java classes that are out
there in pgms to come.

Aaron Bartell

-----Original Message-----
From: Buck Calabro [mailto:Buck.Calabro@commsoft.net]
Sent: Thursday, June 21, 2001 11:15 AM
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
+---

As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.