×
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.
Hi Peter,
If IBM automatically determines the size of the prefix, and provides a
BIF to give us the size of the prefix, you should be able to code your
programs so they are future compatible.
How? How could that possibly be? Using an operational descriptor, I
could probably reinforce future compatibility with a bit of messing
around with pointer logic. But I just don't see how the BIF could
possibly solve this problem without requiring an operational descriptor
or something like that.
Remember, I'm talking about reference parameters. All that's passed
from caller to callee is a pointer. No size, data type, etc is passed.
At least with our existing BIFs like %size(), %len(), %decpos(), the BIF
doesn't know what the caller's actual size is, it just knows what the
local definition is. If the caller's definition doesn't match that, you
have problems.
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
