RE: diff btw Procedures and Routines

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
IF you choose to make it a procedure - put it into a service program, and
not /copy it into every program that uses it.  (Well, maybe you can /copy
the prototype for it.)

Granted there are some that I wanted to make a subprocedure in a service
program but didn't quite have the time to do.  What I did do was change
the program to a prototyped call so that I could use CONST and VARYING on
some of the parameters.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Booth Martin" <Booth@MartinVT.com>
Sent by: rpg400-l-admin@midrange.com
08/15/2002 11:50 AM
Please respond to rpg400-l


        To:     <rpg400-l@midrange.com>
        cc:
        Fax to:
        Subject:        RE: diff btw Procedures and Routines


--
--
[ Picked text/plain from multipart/alternative ]
I've been 5 years trying to get this straight and am still confused.  Lets
say I have a utility program that is a pop-up calendar.  The parm is a
date.
  Should this be a program or a procedure?



---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@MartinVT.com
---------------------------------------------------------

-------Original Message-------

From: rpg400-l@midrange.com
Date: Thursday, August 15, 2002 12:45:09
To: 'rpg400-l@midrange.com'
Subject: RE: diff btw Procedures and Routines

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
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.


.
--
[ Content of type image/gif deleted ]
--

_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@midrange.com
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/cgi-bin/listinfo/rpg400-l
or email: RPG400-L-request@midrange.com
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.