|
At 11:47 07/29/1999 , Chris Bipes wrote: >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? Service programs are useful when you have a library of general purpose or related procedures that are useful in several (many) programs. They are analogous to a DLL in windows. Directly bound modules are most useful when they are used by a small number (one or two or ...) of programs. Modules are like object modules which are linked to create a program. With a service program, you can add additional procedures, or modify an existing one, and (assuming that you don't change the interface) you only need to maintain and recreate one object. With bound modules, you recreate the module, and then you must relink (UPDPGM or CRTPGM) all of the programs that use it. Pete Hall pbhall@execpc.com http://www.execpc.com/~pbhall +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.