Re: Benefits of Sub-procedures -- RPG400-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

Booth Martin wrote:

What fascinates me even more is how many really bright people are getting this stuff wrong. Just as I suspected, this stuff is not as easy as y'all want us huddled masses to believe.

Booth: This ain't rocket science. Barbara was just being overly picky, IMO.

The basic idea of procedures is simple: Break down your task in easy to handle chunks. With smaller chunks of code, it is much easier to spot places where you can reuse code, and much easier to design your procedures so that they are more reusable.

As I said in an earlier note, the procedure (along with the function and the method) is perhaps the single most frequently used structuring technique in practically every other programming language. And perhaps the most important.

If you're used to the RPG III style of CALL/PARM and *ENTRY PLIST, you already understand most of the issues involved. The rest is just additional syntax, functionality, and flexibility, which can be easily learned.

Cheers! Hans

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.