×
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 Klement wrote:
This is different from %addr(). When I do %addr(xx)+2 today, it's my
way of getting the address of the data portion of the VARYING variable.
So %addr(xx:*DATA) makes sense to me in that case.
Heh, we already have %addr(varfld:*DATA) planned for this feature. We
had originally considered having %SIZE(varfld:*something); we couldn't
think of a decent name for the special parameter, which gave us a strong
hint that we were on the wrong track. %addr(x:*data) seems a (much
much) more natural way of coding.
Whereas, something like %len(MyVary: *max) (or your suggestion of
%varysize() which does the same thing) that would give the maximum
amount of CHARACTERS (not bytes) in one fell swoop would be much less ugly.
We hadn't realized until this thread that there was such a need to know
the maximum number of characters a field can hold; %len(string:*MAX) is
how I would do it, for any string type, not just varying, to avoid
having to divide by the character size for ucs2 and dbcs. We'll see ...
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.