× 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.


  1.  Home
  2. RPG400-L
  3. August 2002

Re: diff btw Procedures and Routines

To the programmer, there's not a lot of difference in using a procedure vs a
subroutine.  What I'm trying to say is that you can usually achieve the same
results whether you put your code in a procedure OR a subroutine, BUT:

1) It is easier to see what values the procedure is expecting via the
arguments being passed (tight coupling, which is good)...whereas using the
traditional RPG subroutine it is not always immediately clear which fields
in the program that the subroutine is using and/or possibly modifying (loose
coupling, which is NOT good).

2) Procedures are Cool!

----- Original Message -----
From: "MURALI DHAR" <nmuralidhar@rediffmail.com>
To: <rpg400-l@midrange.com>
Sent: Thursday, August 15, 2002 9:39 AM
Subject: diff btw Procedures and Routines



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 thread ...
Follow-Ups:
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.