|
<Paul> 3. IMHO: OO is paradigm changing and is not easy to initially grasp however it has the capability to reduce development times by orders and magnitude. ... 4. IMHO: It is my assertion that procedural approaches cannot solve business problems with anywhere near the productivity and flexibility that an OO approach yields. </Paul> Just so I am clear on what you are calling "procedural". Do you mean heavy use of RPGILE (*SrvPgm objects)? Or are we talking *PGM objects? I do agree that Java has a decent amount more of flexibility, but I want to make sure we are taking all of RPG's best features into account. RPG is a very modular language where I can reuse components quite easily (talking *SrvPgm's here). I just don't have features like inheritance, abstract classes, overloading, overriding, and interfaces. Here's a quick sample of some RPG code that was developed in a modular fashion. http://mowyourlawn.com/html/RPGMAILExample.php Aaron Bartell
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.