Have you ever heard of the unix command line tool called "grep"? The perl "grep" function is sort of based on that. The tool is used to filter a text stream (a text file, or text data being fed through a "piped" command line) by selecting (or, with the "-v" option, rejecting) lines that match a given regex pattern:
grep -v "^'" file.asp > uncommented_file.asp
To do the same thing with perl, it's still the case that all you need is a command line:
perl -ne 'print unless (/^\x27/)' file.asp > uncommented_file.asp
(In that case, an ms-windows "dos" shell would rather have double quotes instead of single quotes around the "script". Note that I use "\x27" instead of an actual apostrophe character, to avoid quoting problems in the shell.)
If you really need this to be done as part of a larger script that is doing other things with the non-comment lines, you can read all the lines into an array like this:
open( INPUT, "<", $ARGV[0] ) or die "$ARGV[0]: $!\n";
my @code_lines = grep !/^\x27/, <INPUT>;
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: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.