If you can fiddle your sub into a C preprocessor macro, you might want to take a look at the -P option in perlrun or Filter::cpp.
Short intro from the docs
-P NOTE: Use of -P is strongly discouraged because of its inh
+erent
problems, including poor portability.
This option causes your program to be run through the C pr
+eproces-
sor before compilation by Perl. Because both comments and
+ cpp
directives begin with the # character, you should avoid st
+arting
comments with any words recognized by the C preprocessor s
+uch as
"if", "else", or "define".
If you're considering using "-P", you might also want to l
+ook at
the Filter::cpp module from CPAN.
--
Joost downtime n. The period during which a system
is error-free and immune from user input.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link
or How to display code and escape characters
are good places to start.
|