|
Bill Bynum > 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 I wouldn't call that *one* environment. :) > 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. > Programmers are indeed different. I sure wouldn't drop a piece of old code into one of my programs. Perhaps you're reluctant of using API's too, since the code isn't "right in front of you"? +--- | 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 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.