On 2 Sep 2002, Tom Hughes wrote:
> In message <[EMAIL PROTECTED]>
> Tom Hughes <[EMAIL PROTECTED]> wrote:
>
> > That explains why you are not seeing the last component. You are also
> > missing the first one for some reason. The most likely cause would be
> > that you have already used
In message <[EMAIL PROTECTED]>
Tom Hughes <[EMAIL PROTECTED]> wrote:
> That explains why you are not seeing the last component. You are also
> missing the first one for some reason. The most likely cause would be
> that you have already used key_next to discard the first component
> befor
On 2 Sep 2002, Tom Hughes wrote:
> This loop stops as soon as key_next() becomes NULL which means that
> you never process the last key component. I would guess that you want
> to make the first line into this:
>
> while (key != NULL) {
what can i say. OOPS :-)
/j
In message <[EMAIL PROTECTED]>
Josef Hook <[EMAIL PROTECTED]> wrote:
> As you can see above the while loop in multiarray below only iterates
> 4 times when it should iterate 6 times ( .MultiArray[2;3;2;1;1;1] ).
> The same happens when i define a 3 dim array .MultiArray[2;2;2]
> it only i
I've discovered a "feature" when using the new key implementation.
It seems that key_next function dosent walk down the chain of keyes like
the old key->next pointer did.
I've managed to reproduce this behaviour many times.
Consider this pasm code:
new P0, .MultiArray[2;3;2;1;1;1]
