Yes, your regular expression didn't work for me either. I made a regexp that I believe works (below). But, before you use it for real files, try it on some samples to make sure it is doing what you want. Otherwise, you may lose your original c files when you try to change them.
#!/usr/bin/perl
use strict;
use warnings;
open my $fh, "<", 'o33.txt' or die $!;
my $cfile = do {local $/; <$fh>};
close $fh or die $!;
$cfile =~ s/^[\t ]*reports?\((?s:.*?)\);?[\t ]*\n//gm;
print $cfile;
__END__
^[\t ]* optional leading spaces/tabs from beginning of line, (
+the 'm' modifier)
reports? reports with the 's' optional
\( left paren
(?s:.*?) allow '.' to match newline in this scope (between parens)
\) closing paren
;? optional ';'
[\t ]* optional spaces/tabs
\n ends with newline
Chris
Update: added 'tabs' to spaces
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.