RE: Procedures

Thank you.  I was inclined to think the same way but not sure and to lazy to
read all the docs out there.  I am planning on boning up on the subject when
I am thru with sockets.

Christopher K. Bipes            mailto:ChrisB@Cross-Check.com
Sr. Programmer/Analyst          mailto:Chris_Bipes@Yahoo.com
CrossCheck, Inc.                http://www.cross-check.com
6119 State Farm Drive           Phone: 707 586-0551 x 1102
Rohnert Park  CA  94928         Fax: 707 586-1884


-----Original Message-----
From: Tim McCarthy [mailto:TimM@softwarejungle.com]
Sent: Thursday, July 29, 1999 1:01 PM
To: 'MIDRANGE-L@midrange.com'
Subject: RE: Procedures


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.   

+---
| 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
+---