|
hi Charles, > However, I still don't understand why Barbara needed both the MaxPtyAlpha > and the MaxPtyA fields. > > Would not the following have worked? > > D MaxPtyAlpha > D MaxPty1 10i 0 Overlay(MaxPtyAlpha) > D MaxPty2 10i 0 Overlay(MaxPtyAlpha:*next) > ... > D MaxPty8 10i 0 Overlay(MaxPtyAlpha:*next) > D MaxPty9 10i 0 Overlay(MaxPtyAlpha:*next) > D MaxPty 10i 0 Overlay(MaxPtyAlpha) > D Dim(%Div(%Size(MaxPtyAlpha) > D :%Size(MaxPty1))) Think about it... the %size() BIF tells you how big MaxPtyAlpha is. How big is it? In this particular example, it's the size of the larger of two things. Either it's the total size of MaxPty1...MaxPty9, or it's the total size of MaxPty. But you don't know the size of MaxPty, since the size of MaxPty depends on how large the DIM() value is. Since you don't know the size of MaxPty, you CAN'T know the size of MaxPtyAlpha. Do you see what I'm saying? Barbara had declared MaxPtyA as only include MAxPty1 thru MaxPty9. That way, the size of MaxPtyA does not depend on the size of the MaxPty array. Since that's the case, you can use %size(MaxPtyA) as part of the definition for MaxPty...
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.