|
Mark Walter wrote: > That is a little elitist isn't it. It wasn't intended that way. I try to write my programs so that any AS/400 programmer should be able to understand what's going on, regardless of any RPG/II knowledge. Sticking to cycle programming may be a benefit to the programmer who knows the program, but I hate diving into a "cycle program" (even with my 20 years of RPG experience). With the increasing difficulty of getting (young) people to program on the AS/400 platform, we should throw away the "level breaks". It almost made me quit my first S/38 job having to learn the cycle, and I'd only Cobol, Fortran and Basic in my "luggage". One can only imagine what thoughts may run through a Java/C/Python-trained person would think of a "cycle program"... I can't help thinking that one (sub-conscious) reason for sticking with the cycle is "job protection". I hope that I'm wrong, and that it's just lack of time to learn all the new features of ILE RPG.
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.