Comments on: When and How to Upgrade Code http://www.rpgandprogramming.com/2008/12/when-and-how-to-upgrade-code/ Not Role Playing Games, but the RPG programming language and the craft of programming. Tue, 07 Feb 2012 05:48:53 +0000 http://wordpress.org/?v=2.6.3 By: codingRPGfor30yrs http://www.rpgandprogramming.com/2008/12/when-and-how-to-upgrade-code/#comment-218 codingRPGfor30yrs Sun, 01 Mar 2009 01:17:40 +0000 http://www.rpgandprogramming.com/?p=65#comment-218 there's about 80 ways to code what you just showed. I have worked in RPG from 1979 until the present and have seen everything. Code is code, whether indicators used or bifs or whatever.. if you are under the gun to produce changes and create aps, you just code the crap like it currently exists, for readability, not because you like to look up something and decide to put it in a program where the next guy will have to debug it to figure out what its doing..indicators are a reality and we know everything can be done without them..but what is the purpose of re-write if your just adding a screen. Ive seen a program where all *in have been used two times (saved off and reused, all 198 of them) ..ive seen blocks of code commented out with if *inlr *inlr etc.... SO do new stuff in free form, use %bifs, clean up when time permits, imbed SQL whenever possible, test it thoroughly and move on to the next change. be consistent with the code that already exists unless the change is substantial. there’s about 80 ways to code what you just showed. I have worked in RPG from 1979 until the present and have seen everything. Code is code, whether indicators used or bifs or whatever.. if you are under the gun to produce changes and create aps, you just code the crap like it currently exists, for readability, not because you like to look up something and decide to put it in a program where the next guy will have to debug it to figure out what its doing..indicators are a reality and we know everything can be done without them..but what is the purpose of re-write if your just adding a screen. Ive seen a program where all *in have been used two times (saved off and reused, all 198 of them) ..ive seen blocks of code commented out with if *inlr *inlr etc….

SO do new stuff in free form, use %bifs, clean up when time permits, imbed SQL whenever possible, test it thoroughly and move on to the next change. be consistent with the code that already exists unless the change is substantial.

]]>