agreed. this is not my preferred escaping system either, but we can't just go changing it now. i can't think of any way to make such a change backwards compatible.
the best that could be done (if someone is interested in doing it) in 1.x, would be to make escaping behavior configurable via a simple property toggle, but even then, the current behavior would have to stay the default option. On Fri, 25 Feb 2005 11:17:36 -0800, Will Glass-Husain <[EMAIL PROTECTED]> wrote: > Yes. It's confusing. But I'd vote against changing this (for the 1.x > series) or all > my app-generating templates will break. > > WILL > > ----- Original Message ----- > From: "Gonzalo Diethelm" <[EMAIL PROTECTED]> > To: "'Velocity Users List'" <velocity-user@jakarta.apache.org> > Sent: Friday, February 25, 2005 7:09 AM > Subject: RE: Escaping in VTL (was Re: Velocity JSP Generation) > > >> Doesn't quite work that easily. > >> > >> The problem is that if "#directive" is not an actual macro, > >> than \#directive > >> is shown verbatim. You only should escape when the same > >> code is legit in > >> both the source and the generated Velocity. This can be a > >> little confusing. > > > > I know there is no agreement on this. To me, this behavior breaks the > > principle of least astonishment. > > > > http://en.wikipedia.org/wiki/Principle_of_least_astonishment > > > > Regards, > > > > > > -- > > Gonzalo Diethelm > > [EMAIL PROTECTED] > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
