Jeff Young wrote:
A. Make it a service program
B. Make it a bound modue
C. Make it a stand alone program called by others as needed.

IMO, the situations where you bind a module into a program statically are extraordinarily rare. We have a few of them here at MKS because there are situations where we need to call routines but ensure we are not picking up code from the library list.

If there's any chance the routine will be called by more than one program, I would say put it in a service program.

david


This thread ...

Replies:

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

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