RE: Procedures

[Tim McCarthy <TimM@xxxxxxxxxxxxxxxxxx>]

Build a module or a service program? Well a service program can be built
out of several modules so it's never one or the other. Nevertheless
collecting a number of common routines into a service program is a
design decision based on:
Maintainability - you can update or fix the service program without
having to recompile/update every program that uses it (signature values
aside).
Program size - Including a module increases the size of each program
whereas in a service program the code exists once.
Speed - If the routine is small and invoked regularly in the tight
routine you may want it included as a module.
Storage encapsulation - If the code shares variables with other modules
other than through parameters you'll probably have to include it as a
module.
This list is by no means definitive and each reason has exceptions.   

> -----Original Message-----
> From: Chris Bipes [SMTP:ChrisB@cross-check.com]
> Sent: Thursday, July 29, 1999 9:48 AM
> To:   'MIDRANGE-L@midrange.com'
> Subject:      RE: Procedures
> 
> Good questions.  If I need the same subroutine in multiple programs, I
> create a module.  I have created a standard binding directory in which
> I add
> all my modules.  If I call the same program from several other
> programs, for
> example validating the users security to use an application, I create
> a
> service program and add it to my binding directory.  As soon as all
> the
> programmers here learn how to code procedures and bind programs this
> will be
> implemented.  For now it is only in some TCP/IP sockets programs.
> When to
> build a service program or a module is not clear to me.  Any other
> takers?
> What is the benefit to using one over the other?  I would also like to
> know.
> 
> -----Original Message-----
> From: Scott Swaim [mailto:scott@qualitycorps.com]
> Sent: Thursday, July 29, 1999 8:36 AM
> To: MIDRANGE-L@midrange.com
> Subject: Re: Procedures
> 
> 
> Maybe I did not make myself clear enough.  I have figured out how to
> writ
> the code for procedures.
> I don't know where to go from there.
> 
> Do I create a module or bound program?
> do I need a Binding directory?
> How do I compile the module into the binding directory?
> Do I make it a service program?
> etc.
> 
> Scott Swaim
> scott71@hpnc.com
> +---
> | This is the Midrange System Mailing List!
> | To submit a new message, send your mail to MIDRANGE-L@midrange.com.
> | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
> | To unsubscribe from this list send email to
> MIDRANGE-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator:
> david@midrange.com
> +---
+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---