There is a BREAK action for the FOR/WHILE actions, and a @BREAK metatag for @FOR and @WHILE metatags.
It's true that when inside of a TCF, all the auto-scoped variables are incorrectly placed into the request scope, rather than the method scope. Thus the FOR action and even the search action's request$resultset end up in the incorrect places. This rarely causes a problem, however since these variables are almost always reassigned. There are some interesting problems that can arise from this fact though so you always have to be attentive when you're calling a TCF and what's going on inside of it. -----Original Message----- From: Bill Conlon [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 22, 2005 1:48 PM To: [email protected] Subject: Re: Witango-Talk: TCF defect? Ahh. Will this let me break out of FOR/WHILE metatag loop? (as opposed to action). On Tuesday, February 22, 2005, at 10:06 AM, Bill Conlon wrote: > Manual states: > > "This tag does not affect loops initiated with For Loop or While Loop > actions. " > > On Tuesday, February 22, 2005, at 09:14 AM, Bill Downall wrote: > >> Bill Conlon wrote: >>> I want to use a FOR action in a TCF. [I need an action rather than >>> a metatag so I can BREAK out of a loop on a condition.] >> >> Bill, >> >> There is also the <@BREAK> metatag for breaking out of a metatag >> >> Bill >> >> ______________________________________________________________________ >> __ >> 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 ________________________________________________________________________ TO UNSUBSCRIBE: Go to http://www.witango.com/developer/maillist.taf
