RE: Space used by bind by copy vs space used by bind by reference -- MIDRANGE-L

× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.

-----Message d'origine-----
[mailto:midrange-l-bounces@xxxxxxxxxxxx] De la part de David Gibbs
Envoyé : vendredi 26 juin 2009 17:16

Reducing program size is not, IMO, the justification for
using service programs ... maintainability is the primary
reason ... as you only have one object containing the module
that has to be maintained.

Agreed. Even with my lack of experience with service programs, I think I've got the point thanks to this list.
But can you imagine a system where EVERYTHING is bound by copy and there are no service programs? I'm thinking something like " the continual use of bind by copy can lead to unexpected results"

The fact that program size

doesn't expand is gravy (and quite minor ... Disk space is cheap).

Well we are getting fed up with now having to even empty QRPLOBJ because every time a programmer simulates an installation he recompiles practically every program and the disks get filled up. More and more modules becoming interdependant. Each time someone creates a new one it links other modules together. It's like a snowball effect.

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.