×
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.
<Scott>
Complaining that CONST is bad because a variable can still by changed though another non-CONST interface is like complaining that the locks on the front door of your house is bad because burglars can still steal your TV by entering through the back door.
The fault isn't with CONST, it's with the fact that you have two different methods to access the same variable.
Or, that you are lying to the compiler... using a prototype that doesn't match it's corresponding procedure interface.
</Scott>
The fault it's with the compiler, trusting what a prototype pretends, instead of checking the implementation of the called procedure itself, like other compilers do.
<Scott>
VALUE is okay for short things, such as numeric values, but some environments (SQL comes to mind) don't allow VALUE. Then you end up with wrappers, et al.
</Scott>
That's the problem with VALUE (performance is no real issue, we're talking about less than micro seconds).
The real problem is ILE parameter passing!!! There is no strong mechanism to pass parameters, only workarounds available!!!
D*B
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.
midrange.com
