I don't know about Witango per se, but in old mainframe programming we used to assign static variables outside the loop that were going to be used as the loop controller. For example:
<@Assign Local$UpperLimit <@NUMCOLS ARRAY="local$itemInfo">> <@FOR STOP=<@Var Local$UpperLimit>> I am not sure that in Witango the <@Numcols would be evaluated on every entry into the loop but it seems it would. Replacing that with the static variable could help. -----Original Message----- From: William M Conlon [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 08, 2008 10:24 PM To: [email protected] Subject: Re: Witango-Talk: performance with array's Replace @@local$counter with <@CURROW> and eliminate the expression evaluation. Bill On Jan 8, 2008, at 6:40 PM, GK wrote: > Is there a way to improve the performance of the following code: > > > <@FOR STOP=<@NUMCOLS ARRAY="local > $itemInfo">> > <@set local$counter <@calc > expr="@@local$counter+1">> > '@@resultSet[0, @@local > $counter]':'<@var resultSet[1, @@local$counter] > ENCODING='JAVASCRIPT'>', > </@FOR> > > ______________________________________________________________________ > __ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
