[About a bug, maybe he is right, I do not know]

>          #local A = (J  )*zRes+(K  );
>          #local B = (J+1)*zRes+(K  );
>          #local C = (J+1)*zRes+(K+1);
>          #local D = (J  )*zRes+(K+1);
>          <A,B,C>,<A,C,D>,
> But since I was in this part I started to optimize this stuff. Note that
> optimized part is exactly the same as:
>          #local A = (J  )*zRes+(K  );
>          #local B = A + zRes;
>          #local C = A + zRes + 1;
>          #local D = A + 1;
>          <A,B,C>,<A,C,D>,

I do not agree.
Mathematically, you are correct.
But Computationaly, you may end up with overlapping part and holes,
because the way you compute the coordinates are not always
exactly the same when you are iterating in the loop.

Maybe I'm just paranoid.

Post a reply to this message