×
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.
Why bind by copy instead of by reference?
Because it facilitates better code reuse, it provides the ability to
properly encapsulate function, it gives the ability to define a
public and private interface, and it gives almost all the benefits of
dynamic program call without the perceived performance impact.
Obviously, I can't speak for IBM so I can't say what they were thinking when they allowed bind by
copy.
However, my personal feeling is that "code reuse" was not the primary reason for bind by copy; simply
because bind by reference is such a better way to reuse code.
Instead, the other points Simon had: encapsulation, public/private/protected interface are the main
reasons for bind by copy.
If you have a large ILE program, with many procedures that won't be needed outside the one ILE
program, you can use break it up into multiple modules and benefit from the encapsulation resulting
from the modularity.
Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307
wiltc@xxxxxxxxxx
This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.
midrange.com
