On Tue, 11 Jun 2002, Sam Tregar wrote:
> > I thought about this, and i'm wondering how much ppl realy use it in
> > this way. IMHO it should be a "Don't try this, it will break", instead
> > introducing this copy-"workaround". But i think i will use this patch
> > only for my private-version,
On Tue, 11 Jun 2002, Nico Erfurth wrote:
> I thought about this, and i'm wondering how much ppl realy use it in
> this way. IMHO it should be a "Don't try this, it will break", instead
> introducing this copy-"workaround". But i think i will use this patch
> only for my private-version, because
On Tue, 11 Jun 2002, Sam Tregar wrote:
> On Tue, 11 Jun 2002, Nico Erfurth wrote:
>
> > It changes the way arrays/loops are handled.
> > 1.) If you pass in a array-reference, it will be not dereferenced anymore
> > I did this, so i can use a small Wrapper-class, which allows me to
> >
On Tue, 11 Jun 2002, Nico Erfurth wrote:
> It changes the way arrays/loops are handled.
> 1.) If you pass in a array-reference, it will be not dereferenced anymore
> I did this, so i can use a small Wrapper-class, which allows me to
> tie a database-statement to an array, and returning th
Hi,
some weeks ago i did a little "improvement" to HTML::Template, at least i
think it is a improvement ;)
It changes the way arrays/loops are handled.
1.) If you pass in a array-reference, it will be not dereferenced anymore
I did this, so i can use a small Wrapper-class, which allows me to
