What version of UD is that supposed to be true? Seeing this discussion, and an internal one about performance increased, I wrote a small program to test this as well. Had a friend run it on a UV box, and there the timing between a FOR/NEXT and REMOVE loop was basically the same. Or at least close enough to be able to tell. But on UD 6.1, box the timing between the 2 were drastically different... For a 10,000 element dynamic array the FOR/NEXT loop took apx. 16 seconds, while the remove took under 1. The same program running on a UV 9.5.x (IIRC) was under 1 second either way.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Pingilley, Ron Sent: Sunday, April 17, 2005 10:07 AM To: u2-users@listserver.u2ug.org Subject: RE: [U2] Clarification on FOR...NEXT loops Jeff, UV/UD do not keep track of which multi-value was last accessed. Only the attribute. Each iteration of the For-Next had to start counting from the beginning of attribute 1 according to your notes below. If you re-run your test with FOR/NEXT/<I> (instead of <1,I>) you should see a significant improvement in the For-Next time. --Ron P. ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
