|
Crispin Bates wrote:
why not make the %len(myVaryFld:*MAX)
%len(myVaryFld:*DATA)
Because when I see %Len(xx:*DATA) it says to me "I want the length of
the data", which we can already get with the ordinary %len() BIF. What
I really want isn't the length of the data, it's the maximum length that
will fit in the variable. Thus, %len(xx:*MAX).
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.
--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.
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.