×
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.
I have an unenviable task of converting a 16yr old RPG to ILE. It calls a lot of other smaller RPG or modules as we called them before we had ILE. Each one copy booked in from QCPYSRC.
I have to make it 100% ILE as it is intended to run in a named activation group.
At the beginning of the program, it reads in a data area. As I'm not that experienced with data areas, I've already done a little debugging. I noticed that the data area gets modified when LR is on, without coding OUT.
I only found out because the zone I read the data area into got modified somewhere.
I thought I would read in the data area in my main procedure and then directly call a subprocedure with CONST on the parameter to protect my data area. However, from experience I've noticed that it is still possible to modify the parameter inadvertently, and we have already discussed this. Someone said that CONST in reality only means that the parameter is not INTENDED to be changed.
So, I just thought it was a bit ironic : normally, I use CONST on all parameters used for input. But now that I REALLY don't want my parameter to be changed, I shall code VALUE instead.
Unless someone else has a better idea!
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
