At 05:43 PM 9/24/2001 -0400, Brian Hann wrote: >That didn't work. I tested just setting normal scalar variables within the >template, since I figured my OUT.loop.count stuff was wrong; still no >workie. I'm guessing the variables passed to TT are cloned, which makes >them read-only, right? Is there any other way to output select processed >content to multiple variables?
Andy's fix should do it. Yes, variables are cloned, so any new variables are lost before process returns. Since you preset OUT to an empty array you should be ok: although OUT is cloned (but only skin-deep), setting OUT.0, OUT.1 etc should still be visible after process returns. As an aside, it would be nice to have top-level cloning by process be optional, because there are cases, like your's, where you want to get to variable values after process returns. For now you either have to get to the variables inside a POST_PROCESS (since that is inside the clone), or set entries of lists or hashes that already exist. Craig
