>> When a TMPL_LOOP is encountered, H::T needs to create (for want of a
>> better description) a child context, that contains only the template
>> variables for the child. Each child context is effectively a new
>> H::T object, so that the very top H::T object accumulates the output
>> from each
Mathew Robertson ha scritto:
> Hi Hakim,
>
> I think you might be over analysing the problem. :-)
Heh, that is possible :-)
>
> When a TMPL_LOOP is encountered, H::T needs to create (for want of a
> better description) a child context, that contains only the template
> variables for the child
Hi Hakim,
I think you might be over analysing the problem. :-)
When a TMPL_LOOP is encountered, H::T needs to create (for want of a
better description) a child context, that contains only the template
variables for the child. Each child context is effectively a new H::T
object, so that the very
Hakim Cassimally wrote:
> Hi,
>
> We're having an "interesting" problem with a significant slowdown in
> processing of some HTML::Template templates.
The current suspicion, after HTML bod and $boss worked on this,
by a process of elimination is that the problem is when the same
data structure is
Hi,
We're having an "interesting" problem with a significant slowdown in
processing of some HTML::Template templates.
We are using:
- using H::T 2.8 and 2.9
- an house framework that feeds params from a CGI object to H::T
- CGI 2.81 and 3.15
- Perl 5.8.0 and 5.8.4
If the following condit
