×
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.
1) CONST will guarantee to protect parameters _if_ CONST is also
specified in the called program/procedure. In other words caller and
callee should have identical prototypes - preferably via /COPY.
2) CONST will only copy the data _if_ there is a mis-match between the
parm definition and the actual parm passed. Otherwise the original
field is passed.
So if (for example) the callee did not specify CONST _and_ there was
no mis-match then if the callee passed the parm to another program/
procedure without any CONST keyword on its proto there is zero
protection in play and if either the original callee _or_ the final
called routine changed the data it will be reflected back in the
original caller.
CONST is a convention - there is no underlying system support for it.
It is up to the programmer to make sure that he follows all the rules
as well.
Jon Paris
www.Partner400.com
www.SystemiDeveloper.com
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.
midrange.com
