Of course, a properly written source filter will insert #line statements, to keep the error messages in sync with the original file. Once you stack a second source filter on top of that, things become hairy, as then, that second source filter needs to understand #line hints as well, and parse them accordingly. Which is unlikely to be correct. I'm not sure if Filter::Simple implements that, but I found #line very handy when dealing with code generated from templates.

As Perl allows anonymous code structures, I tend to try to avoid code generation from templates and try to use as much anonymous code structures as possible, because then I get the Perl syntax check at initial compile time and not at template compile time, which may be in mid-flight already.

In reply to Re^2: question regarding using Switch.pm in production use by Corion
in thread question regarding using Switch.pm in production use by jfroebe

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.