On Mon, Feb 26, 2001 at 02:56:35PM -0500, Geir Magnusson Jr. wrote:
> > From: Sean Legassick [mailto:[EMAIL PROTECTED]]
> >
> > Well, I'm easy - I just want it to work properly in Torque :-)
> >
> > But - IMHO your suggestion is:
> >
> > a) inefficient because a spurious array gets allocated
>
> Thats true. Not sure that it is that big of a deal, but it's true :)
No, I don't think that is a very big deal either all else being equal...
> > b) unnecessary - as far as I understand it the methods took Object[]
> > params because that's what list literals generated, and now
> > they don't...
>
> Yes, but Texen could [and should] be an independant utility ?
I'm not sure that makes sense - Texen works as a layer on top of
Velocity, so it can't be Velocity independent. And its util classes are
specifically designed to be used within Texen templates (which by
definition must be VTL templates).
> If that's the case, I think it's utility interfaces should provide the most
> flexibility and not be tailored just to work with Velocity.
>
> I don't really have any strong feelings about this - just thought it would
> make Texen more general and useful.
Well I have no strong feelings either other than that the StringUtil
class packaged with Texen should work with Texen :-) :-)
So feel free to either commit my patch or make your change instead
(which is actually less of a code change)...
Cheers,
Sean
--
Sean Legassick
[EMAIL PROTECTED]
Ek is 'n man: niks menslik is vreemd vir my nie
