×
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 got something unexpected compiling a service program and am intrigued.
I defined one of the parms in the procedure interface like this:
D ASLPC 7P 2 Const
since I change the value of that field in the called procedure, the
compiler told me that was a no-no. Just for fun, I changed it to this:
D ASLPC 7P 2 Value
Now it compiles! Is this working as designed? I can pass decimal parms
as VALUE, they can be different sizes in the caller/callee, and the
compiler handles it? The calling program gets back the changed value,
decimal aligned and everything?
I'm going to try some experimenting, but I just didn't think this would
work on parms that get changed.
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
