If I put that code into a separate template, the "heavy lifting" code will have to be moved all the way back up to the top of my application, if I'm planning on using this TT chunk in more than one page. ... so that I don't have to worry that some other part of my app has a conflicting name.
WHen using CGI::Prototype I moved many things into a base class that I wanted to re-use. I had no fears of subroutine name conflicts. My method was simple, but the logic was clear and the results predictable. What exactly are THIS and THAT that they might cause name conflict?

In reply to Re: Mixins (problem in CGI::Prototype and Class::Protototyped with subtemplates) by metaperl
in thread Mixins (problem in CGI::Prototype and Class::Protototyped with subtemplates) by merlyn

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.