Andy Wardley wrote: >This gets my award for "Most Annoying Limitation in the TT2 Parser". I >don't think it can be solved easily in the state-driven TT2 parser, but >it has already been "fixed" in the recursive descent TT3 parser. This is >next on my list of TT3 modules to finish so hopefully we'll be able to >graft the v3 parser into v2 at some point in the future. > How's the performance of TT3 relative to TT2? Are performance implications being considered in its development? I suppose that parsing performance makes no difference once the template is compiled, but TT performance in general is important for web applications that use it to generate their interface.
-myk
