You could plan to run all your Perl sources through the C preprocessor before further use and that way co-opt its functionality. The added benefit is that you can then use all of the C preproprocessor functionality, e.g. macros, defined pre-execution symbols and so on in your Perl code - in fact this particular usage pales into triviality compared with what then becomes possible for projects with complex implementation and/or porting requirements.
#!/usr/bin/perl
#IFDEF COMMENT
#+++
I am a comment - symbol COMMENT is left undefined
So there
Instructions: this file is called fred.plp and should
be run through the C preprocessor with output to fred.pl
- modules could be presourced with the extension .pmp
#---
#ENDIF
my $x = 1;
open my $fh, '<fred';
# etc.
__END__
-
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.
|