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 []
Sent: Thursday, July 29, 1999 8:36 AM
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?

Scott Swaim
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to
| To subscribe to this list send email to
| To unsubscribe from this list send email to
| Questions should be directed to the list owner/operator:

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by 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].