|
A procedure is encapsulated, where a subroutine is not. That is, a procedure can see variables that it defines, but not variables that the main program defines. This makes it a lot easier to determine what a procedure is actually doing and where it's getting it's return value(s). This makes a procedure "stand alone", and can be used in other programs with little modification (modification required for any File I/O may be required). It can be extremely difficult to copy a subroutine to another program, as you have to determine all the variables the subroutine uses, and what these are supposed to be set for, etc... I have been known to break my RPG IV program into Subroutines when it starts getting too large to group the logic. Whether or not these should be broken up into Procedures is probably a personal choice. But, subroutines that calculate a value or such, those I would put into Procedures. Regards, Jim Langston -----Original Message----- From: MURALI DHAR [mailto:nmuralidhar@rediffmail.com] why do we use procedures only in modules in ILE programs?why nt subroutines?whats the diff ...plz kindly answer me Best regards Murali
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.