TechTip: An Easier Way to Process Level Breaks
** This thread discusses the article: TechTip: An Easier Way to Process Level Breaks **
Please let me explain why I use the cycle. I use it as a tool. If I have to write a program that requires level break processing or even a simple report without level breaks, I use the cycle. Why? because it is efficient and the one best way to code in RPG for that given circumstance. I write lots of code in lots of languages, C++, VB, VBA, Java, all flavors of RPG, COBOL, blah, blah, blah. Any of these languages are just tools. That's it. Nothing more. Lets not make this a religious discussion. Any of us should be able to learn any new languages and techniques. but, we should also be able and willing to learn techniques within old languages. I have yet to write a single line of free-form RPG code because none of muy clients wants me to. Currently, I'm working on old COBOL applications for a client. Why? Because the pay's the same. If they want me to code in a language I don't know, I will learn it. BTW, nothing is ever really new and modern. Sure, the interface can change, green screen vs. gui vs. web, but, regardless of the language or its newness, they all have to do the same things: 1) accept input, 2) do something with that input, 3) present output and/or store it somewhere. That's it, no magic, just Input, Processing, Output. After that, it's just syntax. Thanks for letting me vent a bit.
** This thread discusses the article: TechTip: An Easier Way to Process Level Breaks **
Please let me explain why I use the cycle. I use it as a tool. If I have to write a program that requires level break processing or even a simple report without level breaks, I use the cycle. Why? because it is efficient and the one best way to code in RPG for that given circumstance. I write lots of code in lots of languages, C++, VB, VBA, Java, all flavors of RPG, COBOL, blah, blah, blah. Any of these languages are just tools. That's it. Nothing more. Lets not make this a religious discussion. Any of us should be able to learn any new languages and techniques. but, we should also be able and willing to learn techniques within old languages. I have yet to write a single line of free-form RPG code because none of muy clients wants me to. Currently, I'm working on old COBOL applications for a client. Why? Because the pay's the same. If they want me to code in a language I don't know, I will learn it. BTW, nothing is ever really new and modern. Sure, the interface can change, green screen vs. gui vs. web, but, regardless of the language or its newness, they all have to do the same things: 1) accept input, 2) do something with that input, 3) present output and/or store it somewhere. That's it, no magic, just Input, Processing, Output. After that, it's just syntax. Thanks for letting me vent a bit.
Comment