Paul Hoffman wrote: > I may have misunderstood this (my TT experience is minimal), but it > seems to me that in general, if you use this FLUSH you must make a > clear distinction between templates that may be INCLUDEd or whatnot > inside a looping control structure, and those that may not.
Absolutely. This is the primary problem with the current code: it requires the template author to understand some of the logic behind the toolkit in order to know where FLUSH will work and where it will cause problems. > Or maybe your solution can be refined so there's a way to detect outer > blocks automatically. I imagine a stack would figure in any such > refinement, but I'm too new to TT to venture any further than that. Yes, I think the right thing to do is to walk the stack and flush the output of each block, but unfortunately I don't think the current architecture of the toolkit supports this. -myk
